mcp-outbound-infrastructure-fingerprint
LocalAbout mcp-outbound-infrastructure-fingerprint
An MCP server wrapping Mamba Labs’ Apify actor to identify whether a company runs cold email outbound and what infrastructure it uses. It is aimed at teams researching company outreach operations, with sending-domain discovery as a key signal.
Key features
- 01Single-domain and batch analysis
- 02Outbound activity classification
- 03Sending-domain and platform detection
- 04Email infrastructure and DNS checks
- 05Evidence strings and confidence scores
Use cases
- 01Researching a company’s outbound email activity
- 02Identifying candidate sending domains
- 03Reviewing SPF, DKIM, and DMARC status
MCP support
Exposes the `fingerprint_outbound_infrastructure` tool to MCP clients. It sends domains and scan options to the Apify actor and returns its analysis.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprintAPIFY_TOKENSecretApify API token from https://console.apify.com/account/integrationsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
1Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| domain | string | No | A single company domain, e.g. smartlead.ai. Provide either domain or domains. |
| domains | array | No | Batch mode: several company domains analyzed in one call. Takes precedence over domain. |
| skipCache | boolean | No | Force a fresh analysis and ignore the 7 day result cache. |
| dns_timeout_ms | integer | No | Per DNS lookup timeout in milliseconds, 1000 to 15000, default 4000. |
| request_timeout_ms | integer | No | Per HTTP request timeout in milliseconds, 3000 to 20000, default 9000. |
| check_deliverability | boolean | No | Add a blacklist check and a 0-100 health score by running the separate Domain Deliverability Checker actor, which bills its own per-domain rate on top of this one. Default false. SPF, DKIM and DMARC are read from DNS either way. |
| scan_sending_domains | boolean | No | Scan for lookalike sending domains. Default true. This is the strongest signal and the slowest step; turning it off makes runs fast but caps the verdict at what platform and deliverability signals alone can prove. |
| sending_domain_depth | enum | No | deep (default) checks .com, .co, .io, .net and .org. standard drops .net and .org for slightly fewer DNS lookups, at the cost of missing sending domains on those TLDs.deep | standard |
| max_sending_domain_probes | integer | No | Cap on how many candidate sending domains are probed per company, 10 to 300, default 80. Lower it to bound run time and cost on companies with many lookalike domains. |
Details
From the project READMEOutbound Infrastructure Fingerprint MCP Server
MCP server for the Mamba Labs Outbound Infrastructure Fingerprint 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
| Input | Type | Notes |
|---|---|---|
domain | string | One company domain. |
domains | string[] | Batch. Takes precedence over domain. |
scan_sending_domains | boolean | Default true. The strongest signal and the slowest step. |
sending_domain_depth | deep | standard | Default deep (.com .co .io .net .org). |
check_deliverability | boolean | Default false. Adds a separately billed blacklist check and health score. |
skipCache | boolean | Ignore the 7 day result cache. |
max_sending_domain_probes | integer | 10 to 300, default 80. Cap on candidate sending domains probed per company. |
request_timeout_ms | integer | 3000 to 20000, default 9000. Per HTTP request timeout. |
dns_timeout_ms | integer | 1000 to 15000, default 4000. Per DNS lookup timeout. |
max_charge_usd | number | Optional 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:
| Event | Price per event (USD) | Fires when |
|---|---|---|
actor-start | $0.00005 | Charged once when the run starts. |
domain-analyzed | $0.004 on the Free plan, down to $0.0034 on higher Apify plans | Charged 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
{
"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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.