Is Outbound Infrastructure Fingerprint free?

Yes, Outbound Infrastructure Fingerprint is free to use.

How do I install Outbound Infrastructure Fingerprint?

Outbound Infrastructure Fingerprint is a local plugin. Install it using npm package: @mambalabsdev/mcp-outbound-infrastructure-fingerprint and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Outbound Infrastructure Fingerprint safe to use?

Yes. Outbound Infrastructure Fingerprint passed MCP Marketplace's automated security scan with a score of 9.3/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Outbound Infrastructure Fingerprint need?

Outbound Infrastructure Fingerprint requires the following credentials or environment variables: APIFY_TOKEN. You can find setup instructions on the server detail page.

What AI apps work with Outbound Infrastructure Fingerprint?

Outbound Infrastructure Fingerprint uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Outbound Infrastructure Fingerprint MCP Server

by mambabuilt

Developer ToolsLow Risk9.3Local

Free

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

About

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

Security Report

9.3

Low Risk9.3Low Risk

Valid MCP server (2 strong, 3 medium validity signals). 1 known CVE in dependencies (0 critical, 1 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (153/153 approved).

9 files analyzed · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Apify API token from https://console.apify.com/account/integrationsRequired

Environment variable: APIFY_TOKEN

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub README.

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`

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.