Back to Browse

Outbound Infrastructure Fingerprint MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

5.2
Moderate5.2Moderate Risk

This MCP server is well-structured and secure. It properly requires an APIFY_TOKEN environment variable for authentication, validates all inputs using Zod schema validation, and safely constructs API calls without code injection risks. The server has appropriate error handling and provides clear feedback for various failure modes. Permissions are well-scoped to the server's purpose of fingerprinting outbound infrastructure via the Apify API. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

3 files analyzed · 7 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.

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.

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

npm MCP License: MIT

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.

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.

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.

Reviews

No reviews yet

Be the first to review this server!