MCP.Market

Outbound Infrastructure Fingerprint MCP server

by mambabuilt.com·com.mambabuilt/mcp-outbound-infrastructure-fingerprint·v1.3.0

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

0 stars91 downloads/wk

Reviews

Write one

Nobody has reviewed Outbound Infrastructure Fingerprint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Outbound Infrastructure Fingerprint tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • fingerprint_outbound_infrastructure

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Outbound Infrastructure Fingerprint compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
91
more than 61% of 12,191 servers with a package

What its tools let an agent do: 1 read

Release history: 3 versions in the registry since 2026-08-13, latest 2026-10-16, typically one every 54 days.

Install Outbound Infrastructure Fingerprint in Claude Code, Cursor or VS Code

Runs npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-outbound-infrastructure-fingerprint -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint
Add to Cursor

What the publisher says

From the Outbound Infrastructure Fingerprint repository's README, as published. We do not edit it. Read it on GitHub

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

fingerprintoutboundinfrastructure

Returns a flat row per domain: runsoutbound (program, light, none, unknown), confidence, sendingdomains[], registrationclusters[], sendingplatforms[], inboxprovider, warmupdetected, infrastructurevendors[], spfstatus, dkimstatus, dmarcpolicy, 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 brandiscommonword 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 sendingplatforms 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.

Nothing above is checked by us. What we check is on the safety report.

Outbound Infrastructure Fingerprint: common questions

Is Outbound Infrastructure Fingerprint MCP server safe?
Mostly: it is graded B (77/100). Read the Outbound Infrastructure Fingerprint safety report
How do I install Outbound Infrastructure Fingerprint?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Outbound Infrastructure Fingerprint need an API key?
Yes. The registry entry asks for APIFY_TOKEN.
Is Outbound Infrastructure Fingerprint maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v1.3.0.
How does Outbound Infrastructure Fingerprint compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from mambabuilt.com →