Skills/npm/mcp-gtm-suite

mcp-gtm-suite@1.14.4

VERIFIED

Publisher claims: "21 Mamba Labs account-intelligence MCP tools in one server: identity, signals, ICP. Clay-ready." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher mambalabsdev · publishing for 166 daysInstalls 0Last detonated 3d ago
$claude mcp add mcp-gtm-suite -- npx -y @mambalabsdev/mcp-gtm-suite
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
APIFY_TOKENConfiguration, not credentials: MAMBA_MCP_POLL_INTERVAL_MS
Where it talks to
apify.com (its own)Also linkedin.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names linkedin.com as well as its own vendor. The guard injects APIFY_TOKEN only into requests to apify.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets APIFY_TOKEN=apify.com -- npx -y @mambalabsdev/mcp-gtm-suite

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-11 and scored it 92/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 24 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.3sprocessdependency install exit 0
24sclaimed21 tools: scan_gtm_hiring_signals, detect_gtm_tech_stack, aggregate_gtm_signals, scan_job_board_keywords, resolve_linkedin_url, score_icp_fit, resolve_company_identity, enrich_company_firmographics, map_company_social_presence, get_funding_press_signals, get_company_changes, detect_ai_tooling, fingerprint_outbound_infrastructure, track_publication_cadence, push_leads_to_sequencer, audit_agent_accessibility, classify_contact, map_company_event_presence, resolve_legal_entity, monitor_public_awards, capture_linkedin_posts_and_commenters
24sprocessscript backend runs setup only
24sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:16 · File permission modification command — agent changes file ownership/permissions"build": "tsc && chmod +x build/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

No other findings across 1,485 lines in 6 files.

Cost to the agent

Instructions loaded
≈104 tok
1 file · 6 in bundle
Tool list per prompt
≈14,625 tok
21 tools · 696 per tool
Handshake
1023 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 745

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @mambalabsdev/mcp-gtm-suite@1.14.4 as of 3d ago. This is the package itself, not its dependencies.