Gtm Suite MCP Server

@mambalabsdev/mcp-gtm-suite npm v1.8.0

Published by @mambalabsdev — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for the full Mamba Labs GTM Suite. Exposes all eleven account-intelligence actors as tools in one server via Apify: identity resolution, firmographics, social presence, hiring signals, tech stack, job board scanner, funding and press, change fe

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 21

Each tool and what it can reach — statically extracted from the published source.

  • audit_agent_accessibilityingests untrusted input
  • map_company_event_presenceingests untrusted input
  • map_company_social_presenceingests untrusted input
  • aggregate_gtm_signalsno sensitive capability
  • capture_linkedin_posts_and_commentersno sensitive capability
  • classify_contactno sensitive capability
  • detect_ai_toolingno sensitive capability
  • detect_gtm_tech_stackno sensitive capability
  • enrich_company_firmographicsno sensitive capability
  • fingerprint_outbound_infrastructureno sensitive capability
Show 11 more tools ↓
  • get_company_changesno sensitive capability
  • get_funding_press_signalsno sensitive capability
  • monitor_public_awardsno sensitive capability
  • push_leads_to_sequencerno sensitive capability
  • resolve_company_identityno sensitive capability
  • resolve_legal_entityno sensitive capability
  • resolve_linkedin_urlno sensitive capability
  • scan_gtm_hiring_signalsno sensitive capability
  • scan_job_board_keywordsno sensitive capability
  • score_icp_fitno sensitive capability
  • track_publication_cadenceno sensitive capability

What this scan could not see

Versions 6

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.8.0 latest A 96/100 0 1.13.0 2026-09-07
v1.7.0 A 96/100 0 1.12.1 2026-08-13
v1.5.0 A 96/100 0 1.12.1 2026-08-12
v1.4.0 A 96/100 0 1.12.1 2026-08-09
v1.3.0 A 96/100 0 1.12.1 2026-08-07
Show 1 more version ↓
v1.1.0 A 96/100 0 1.12.1 2026-08-06

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mambalabsdev-mcp-gtm-suite/badge.svg)](https://mcptrustchecker.com/registry/mambalabsdev-mcp-gtm-suite)
HTML
<a href="https://mcptrustchecker.com/registry/mambalabsdev-mcp-gtm-suite"><img src="https://mcptrustchecker.com/registry/mambalabsdev-mcp-gtm-suite/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mambalabsdev-mcp-gtm-suite/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @mambalabsdev/mcp-gtm-suite --online

Use the free API → How scoring works

More in API Development