com.mambabuilt/mcp-outbound-infrastructure-fingerprint
NPM · @MAMBALABSDEV/MCP-OUTBOUND-INFRASTRUCTURE-FINGERPRINT · SCANNED SEP 24
Detect whether a company runs cold outbound, on what stack, and from which sending domains.
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 41 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 565 tokens (~565/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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.mambabuilt/mcp-outbound-infrastructure-fingerprint server?
com.mambabuilt/mcp-outbound-infrastructure-fingerprint runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-outbound-infrastructure-fingerprint
claude mcp add com-mambabuilt-mcp-outbound-infrastructure-finge -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint
{
"mcpServers": {
"com-mambabuilt-mcp-outbound-infrastructure-finge": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
]
}
}
} {
"servers": {
"com-mambabuilt-mcp-outbound-infrastructure-finge": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
]
}
}
} codex mcp add com-mambabuilt-mcp-outbound-infrastructure-finge -- npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint
{
"$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
}
}
} openclaw mcp add com-mambabuilt-mcp-outbound-infrastructure-finge --command npx --arg -y --arg @mambalabsdev/mcp-outbound-infrastructure-fingerprint
mcp_servers:
com-mambabuilt-mcp-outbound-infrastructure-finge:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-outbound-infrastructure-fingerprint"] {
"McpServers": {
"com-mambabuilt-mcp-outbound-infrastructure-finge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
]
}
}
} assistant mcp add com-mambabuilt-mcp-outbound-infrastructure-finge -t stdio -c npx -a -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint
{
"mcpServers": {
"com-mambabuilt-mcp-outbound-infrastructure-finge": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-outbound-infrastructure-fingerprint"
]
}
}
} 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.
- 24 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/@mambalabsdev/mcp-outbound-infrastructure-fingerprint@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fingerprint_outbound_infrastructure Fingerprint Outbound Infrastructure ~565
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_deliverability | boolean | – | 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… |
| dns_timeout_ms | integer | – | Per-DNS-lookup timeout in milliseconds. |
| domain | string | – | A single company domain, e.g. smartlead.ai. Provide either domain or domains. |
| domains | array | – | Batch mode: several company domains analyzed in one call. Takes precedence over domain. |
| max_sending_domain_probes | integer | – | Cap on how many candidate sending domains are probed per company. Lower it to bound run time and cost on companies with many lookalike domains. |
| request_timeout_ms | integer | – | Per-HTTP-request timeout in milliseconds. |
| scan_sending_domains | boolean | – | 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_depth | string | – | 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. |
| skipCache | boolean | – | Force a fresh analysis and ignore the 7 day result cache. |
No output schema declared.
No examples provided.
What is the com.mambabuilt/mcp-outbound-infrastructure-fingerprint server?
com.mambabuilt/mcp-outbound-infrastructure-fingerprint is listed in the public MCP registry as com.mambabuilt/mcp-outbound-infrastructure-fingerprint. Detect whether a company runs cold outbound, on what stack, and from which sending domains. This page covers its npm package (@mambalabsdev/mcp-outbound-infrastructure-fingerprint).
Is the com.mambabuilt/mcp-outbound-infrastructure-fingerprint server safe to use?
com.mambabuilt/mcp-outbound-infrastructure-fingerprint scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-outbound-infrastructure-fingerprint server expose?
com.mambabuilt/mcp-outbound-infrastructure-fingerprint exposes 1 tool: fingerprint_outbound_infrastructure. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-outbound-infrastructure-fingerprint server still maintained?
com.mambabuilt/mcp-outbound-infrastructure-fingerprint is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-outbound-infrastructure-fingerprint server under?
com.mambabuilt/mcp-outbound-infrastructure-fingerprint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.