MCP Tools DirectoryAbout this integration
Detect whether a company runs cold outbound, on what stack, and from which sending domains.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.1.1
- Package
- @mambalabsdev/mcp-outbound-infrastructure-fingerprint
- Last compatibility test
- Not independently tested
Connect your agent
@mambalabsdev/mcp-outbound-infrastructure-fingerprintPublisher documentation and package manifest were reviewed. The documented operation is read-only but consumes Apify credits. The package, provider, and integration endpoint were not executed or independently security-audited.
Capabilities: Analyze public domain and mail-infrastructure signals, Report outbound-program confidence, sending domains, platforms, and evidence
Connected profiles
Additional details
com.mambabuilt/mcp-outbound-infrastructure-fingerprint
Source ↗ · Checked 2026-09-171.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17APIFY_TOKEN
Source ↗ · Checked 2026-09-17@mambalabsdev/mcp-outbound-infrastructure-fingerprint
Source ↗ · Checked 2026-09-191.1.1
Source ↗ · Checked 2026-09-19Node.js 18+ stdio wrapper launched with npx and backed by the documented Apify actor.
Source ↗ · Checked 2026-09-19Requires APIFY_TOKEN obtained from an Apify account.
Source ↗ · Checked 2026-09-19Configure the MCP client to run npx -y @mambalabsdev/mcp-outbound-infrastructure-fingerprint with APIFY_TOKEN in its environment.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19