Mcp Outbound Infrastructure Fingerprint

com.mambabuilt由 mambabuilt.com 发布v1.3.1更新于 Nov 7, 2026

Detect whether a company runs cold outbound, on what stack, and from which sending domains.

已验证STDIO仅桌面网页搜索与抓取商业与电商

概览

AI 生成的概览

本地 MCP 服务器，通过 Apify actor 根据公司域名判断其是否在做冷邮件外呼以及使用什么技术栈。

可以做什么
  • 对单个公司域名或一批域名进行冷邮件外呼特征分析
  • 返回 runs_outbound 判定（program、light、none、unknown），并附置信度和可引用的证据
  • 报告发信域名、注册聚类、发信平台、收件服务商、预热情况和基础设施供应商
  • 检查 SPF、DKIM 与 DMARC 配置，可选另计费的可达性与黑名单检查
  • 可调整扫描深度、探测数量上限、超时、跳过缓存以及单次调用费用上限
适用场景
适合销售、GTM 或调研场景：需要判断潜在客户或竞争对手是否真的在做冷邮件外呼、使用哪套发信栈和哪些域名，而不必手工排查 DNS。
运行要求
通过 npx 以 stdio 在本地运行，需要 Node.js。需要 Apify 账号和 APIFY_TOKEN 环境变量，底层 actor 的费用计入该 Apify 账号。调用 actor 需要网络访问。
安装前请注意
每次运行都会消耗 Apify 额度：包含启动费和按域名计费，即使没有外呼信号或域名无法解析也照常计费。可选的可达性检查单独计费，可用 max_charge_usd 限制花费。APIFY_TOKEN 属于机密，不应外泄。结果为启发式判断：品牌词为常见英文单词时置信度会被压低，发信平台的识别率也只是部分覆盖。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Outbound Infrastructure Fingerprint，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Outbound Infrastructure Fingerprint MCP Server

[npm] [MCP] [License: MIT]

[Outbound Infrastructure Fingerprint MCP server]

MCP server for the Mamba Labs Outbound Stack Detector actor on Apify.

Give it a company domain. It tells your agent whether that company runs cold email outbound, and on what stack.

Tool

fingerprint_outbound_infrastructure

InputTypeNotes
domainstringOne company domain.
domainsstring[]Batch. Takes precedence over domain.
scan_sending_domainsbooleanDefault true. The strongest signal and the slowest step.
sending_domain_depthdeep | standardDefault deep (.com .co .io .net .org).
check_deliverabilitybooleanDefault false. Adds a separately billed blacklist check and health score.
skipCachebooleanIgnore the 7 day result cache.
max_sending_domain_probesinteger10 to 300, default 80. Cap on candidate sending domains probed per company.
request_timeout_msinteger3000 to 20000, default 9000. Per HTTP request timeout.
dns_timeout_msinteger1000 to 15000, default 4000. Per DNS lookup timeout.
max_charge_usdnumberOptional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

Returns a flat row per domain: runs_outbound (program, light, none, unknown), confidence, sending_domains[], registration_clusters[], sending_platforms[], inbox_provider, warmup_detected, infrastructure_vendors[], spf_status, dkim_status, dmarc_policy, and an evidence[] array of quotable strings.

What it actually detects

A real outbound program does not send from the domain the business runs on. It buys lookalikes (getcompany.com, company-mail.com, trycompany.co), gives them their own mail tenant, and redirects their web root at the real site. That redirect is the attribution handle, and finding those domains is the part nobody else does.

Measured on nine live domains: 6 of 6 detected on companies that demonstrably run outbound, 0 false positives of 3 on controls.

Two honest limits. When the brand token is an ordinary English word (Gong, Clay, Ramp), lookalike patterns collide with unrelated businesses that legitimately own them; the actor sets brand_is_common_word and caps confidence rather than reporting a confident none. And sending-platform recall is partial by design: Instantly, Smartlead, Lemlist, Apollo and Salesloft connect over OAuth to a customer's own mailbox and publish no SPF include host at all, so an empty sending_platforms tells you little while a populated one is solid.

Pricing

You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:

EventPrice per event (USD)Fires when
actor-start$0.00005Charged once when the run starts.
domain-analyzed$0.004 on the Free plan, down to $0.0034 on higher Apify plansCharged once per domain analyzed. Domains that return no outbound signals, or that do not resolve, still count as analyzed and are charged.

The actor's Apify page carries the current prices. Running this server consumes Apify credits.

Setup

json
{  "mcpServers": {    "mamba-outbound-infrastructure-fingerprint": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-outbound-infrastructure-fingerprint"],      "env": { "APIFY_TOKEN": "your-apify-token" }    }  }}

Get a token at console.apify.com/account/integrations. Read-only; consumes Apify credits per domain analyzed.

Also available

This tool is also exposed by the GTM Suite umbrella server, alongside the rest of the Mamba Labs GTM actors, if you would rather run one server than many.

Built by Mamba Labs.

来源：README.md，提交 55e1163

工具

1

fingerprint_outbound_infrastructure

Fingerprint Outbound Infrastructure

Given a company domain, determine whether that company runs cold email outbound and on what stack. Returns a runs_outbound verdict of program (a deliberate cold outbound setup), light (one weak signal), none, or unknown, plus the evidence behind it. The strongest signal is the lookalike sending domains a real outbound program leaves behind: domains like getcompany.com or company-mail.com that carry their own mail and redirect back to the primary site. Also returns the inbox provider (Google Workspace, Microsoft 365 and others) for the primary domain and each sending domain, any detected sending platform (Outreach, Salesloft, Lemlist, Instantly, Smartlead, Apollo and more), registration clusters showing sending domains bought on the same day, cold email infrastructure vendors, and deliverability posture (SPF, DKIM, DMARC). Note that sending platform recall is partial by design: sequencers that connect over OAuth to a customer's own mailbox leave no DNS trace, so an empty sending_platforms means little while a populated one is solid. Public DNS and HTTP redirects only, no login, no mailbox access. Returns flat Clay-ready JSON. Reads public data and writes nothing; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.

输入参数domaindomainsskipCachedns_timeout_msmax_charge_usdrequest_timeout_mscheck_deliverabilityscan_sending_domainssending_domain_depthmax_sending_domain_probes

版本历史

5
  1. v1.3.1最新Nov 5, 2026
  2. v1.3.0Oct 16, 2026
  3. v1.2.1Oct 6, 2026
  4. v1.2.0Oct 6, 2026
  5. v1.1.1Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分