mcp-outbound-infrastructure-fingerprint

mcp-outbound-infrastructure-fingerprint is a plugin for Cursor from mambalabsdev/mcp-outbound-infrastructure-fingerprint. Its token cost is not measured, scanned A, original, MIT.

A company-domain lookup tool that identifies whether a business uses cold-email outreach, which services support it, and related sending domains. Cold email means unsolicited business email.

In plain words
What is it for?
Use it to research competitors’ email operations, investigate sending domains, and study outbound infrastructure.
Why use it?
It makes otherwise scattered clues about a company’s outbound email setup easier to inspect.

Plugin for Cursor

Written for Cursor: a Cursor plugin manifest.

Good fit Use it to research competitors’ email operations, investigate sending domains, and study outbound infrastructure.

Compare 6 plugins from other repositories ↓
Install with agentmods
npx agentmods add plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/mambalabsdev/mcp-outbound-infrastructure-fingerprint

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-outbound-infrastructure-fingerprint

README.md
[![agentmods](https://agentmods.dev/badge/plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint/github.svg)](https://agentmods.dev/plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint)
Your own site
<a href="https://agentmods.dev/plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint"><img src="https://agentmods.dev/badge/plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-outbound-infrastructure-fingerprint

Your own site · 80×15
<a href="https://agentmods.dev/plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint"><img src="https://agentmods.dev/badge/plugins/mambalabsdev/mcp-outbound-infrastructure-fingerprint/mcp-outbound-infrastructure-fingerprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

mcp-outbound-infrastructure-fingerprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor-plugin/plugin.json · 33 lines

What it actually says

{
  "name": "mcp-outbound-infrastructure-fingerprint",
  "displayName": "Outbound Infrastructure Fingerprint",
  "version": "1.0.0",
  "description": "MCP server for the Mamba Labs Outbound Infrastructure Fingerprint actor on Apify. Give it a company domain and it returns whether that company runs cold email outbound and on what stack, including the lookalike sending domains behind the program, as flat Clay-ready JSON.",
  "author": {
    "name": "Mamba Labs",
    "email": "[email protected]"
  },
  "homepage": "https://mambabuilt.com",
  "repository": "https://github.com/mambalabsdev/mcp-outbound-infrastructure-fingerprint",
  "license": "MIT",
  "logo": "https://mmg-brand-assets.netlify.app/apify-actor-pngs/apify_webhook.png",
  "category": "productivity",
  "tags": [
    "cold-email",
    "outbound",
    "sending-domains",
    "deliverability",
    "apify",
    "clay"
  ],
  "keywords": [
    "mcp",
    "model-context-protocol",
    "cold-email",
    "outbound",
    "sending-domains",
    "apify",
    "clay"
  ],
  "mcpServers": ".mcp.json"
}
Contents

What it installs

The manifest is a name and a version. 2 MCP servers travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 33 lines scan A b62080946978

Subscribe to this mod's changes

mcp-outbound-infrastructure-fingerprint is a plugin published in the GitHub repository mambalabsdev/mcp-outbound-infrastructure-fingerprint (0 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.