Mcp Outbound Infrastructure Fingerprint

Overview

Mcp Outbound Infrastructure Fingerprint is a Model Context Protocol (MCP) server: Detect whether a company runs cold outbound, on what stack, and from which sending domains. In practice that means any MCP-compatible AI assistant can call Mcp Outbound Infrastructure Fingerprint's tools directly — the model decides when to use them in a conversation or agent run.

It runs locally: the npm package @mambalabsdev/mcp-outbound-infrastructure-fingerprint speaks MCP over stdio on your machine. Configuration happens through environment variables — you'll need APIFY_TOKEN. The current release is v1.1.1, published under the MIT license, with source at mambalabsdev/mcp-outbound-infrastructure-fingerprint on GitHub.

Mcp Outbound Infrastructure Fingerprint is listed under Cloud Service on mcp.site and works with any MCP client — Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed and the rest of the ecosystem — using the install snippets below. If you maintain Mcp Outbound Infrastructure Fingerprint for mambabuilt.com, claim this listing to verify ownership, earn the Verified badge, and keep the details current.

Installation

// claude_desktop_config.json
{
  "mcpServers": {
    "mcp_outbound_infrastructure_fingerprint": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
      ],
      "env": {
        "APIFY_TOKEN": "<apify-token>"
      }
    }
  }
}

Requires APIFY_TOKEN