English Français العربية

com.mambabuilt/mcp-outbound-infrastructure-fingerprint

Official registry Cloud and DevOps

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @mambalabsdev/mcp-outbound-infrastructure-fingerprint
Claude Code 
claude mcp add mcp-outbound-infrastructure-fingerprint -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint@1.3.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcp-outbound-infrastructure-fingerprint": {
            "command": "npx",
            "args": [
                "-y",
                "@mambalabsdev/mcp-outbound-infrastructure-fingerprint@1.3.0"
            ],
            "env": {
                "APIFY_TOKEN": "<your apify_token>"
            }
        }
    }
}

Environment variables

  • APIFY_TOKEN required secret Apify API token from https://console.apify.com/account/integrations

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Outbound Infrastructure Fingerprint MCP Server
  2. Tool
  3. What it actually detects
  4. Pricing
  5. Setup
  6. Also available

Outbound 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
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

{
  "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.

Frequently asked questions

What is com.mambabuilt/mcp-outbound-infrastructure-fingerprint?

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

How do I install com.mambabuilt/mcp-outbound-infrastructure-fingerprint?

It runs on your machine. In Claude Code: claude mcp add mcp-outbound-infrastructure-fingerprint -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint@1.3.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does com.mambabuilt/mcp-outbound-infrastructure-fingerprint need an API key?

Yes. It expects APIFY_TOKEN, which you set in its configuration.

Is com.mambabuilt/mcp-outbound-infrastructure-fingerprint open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains com.mambabuilt/mcp-outbound-infrastructure-fingerprint?

It is published by mambalabsdev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.