Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-outbound-infrastructure-fingerprint

NPM · @MAMBALABSDEV/MCP-OUTBOUND-INFRASTRUCTURE-FINGERPRINT · SCANNED AUG 7

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

Available components

npm · @mambalabsdev/mcp-outbound-infrastructure-fingerprint 62
62 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 491 tokens (~491/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mambalabsdev/mcp-outbound-infrastructure-fingerprint

# add to Claude Code
claude mcp add com-mambabuilt-mcp-outbound-infrastructure-finge -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint
# add to Codex CLI
codex mcp add com-mambabuilt-mcp-outbound-infrastructure-finge -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-outbound-infrastructure-finge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mambabuilt-mcp-outbound-infrastructure-finge --command npx --arg -y --arg @mambalabsdev/mcp-outbound-infrastructure-fingerprint
# ~/.hermes/config.yaml
mcp_servers:
  com-mambabuilt-mcp-outbound-infrastructure-finge:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-outbound-infrastructure-fingerprint"]
// mcp.json
{
  "mcpServers": {
    "com-mambabuilt-mcp-outbound-infrastructure-finge": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Aug 26 +27
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 6 Aug 26 35

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Aug 2026 · Analysed npm/@mambalabsdev/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 95 packages
Packages resolved 95
Deprecated 92
Stale 29
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools · 1 exposed · ~491 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
fingerprint_outbound_infrastructure ~491

Given a company domain, determine whether that company runs cold email outbound and on what stack. Returns a runs_outbound verdict of program (a deliberate cold outbound setup), light (one weak signal), none, or unknown, plus the evidence behind it. The strongest signal is the lookalike sending domains a real outbound program leaves behind: domains like getcompany.com or company-mail.com that carry their own mail and redirect back to the primary site. Also returns the inbox provider (Google Workspace, Microsoft 365 and others) for the primary domain and each sending domain, any detected sending platform (Outreach, Salesloft, Lemlist, Instantly, Smartlead, Apollo and more), registration clusters showing sending domains bought on the same day, cold email infrastructure vendors, and deliverability posture (SPF, DKIM, DMARC). Note that sending platform recall is partial by design: sequencers that connect over OAuth to a customer's own mailbox leave no DNS trace, so an empty sending_platforms means little while a populated one is solid. Public DNS and HTTP redirects only, no login, no mailbox access. Returns flat Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.

NameTypeReqDescription
check_deliverabilityboolean–Add a blacklist check and a 0-100 health score by running the separate Domain Deliverability Checker actor, which bills its own per-domain rate on top of this one. Default false. SPF, DKIM and DMARC…
domainstring–A single company domain, e.g. smartlead.ai. Provide either domain or domains.
domainsarray–Batch mode: several company domains analyzed in one call. Takes precedence over domain.
scan_sending_domainsboolean–Scan for lookalike sending domains. Default true. This is the strongest signal and the slowest step; turning it off makes runs fast but caps the verdict at what platform and deliverability signals al…
sending_domain_depthstring–deep (default) checks .com, .co, .io, .net and .org. standard drops .net and .org for slightly fewer DNS lookups, at the cost of missing sending domains on those TLDs.
skipCacheboolean–Force a fresh analysis and ignore the 7 day result cache.

No output schema declared.

No examples provided.