48
/ 100
22 days ago
glama

GTM MCP Server

A unified MCP server that connects HubSpot, Clay, Apollo, Slack, and email to enable AI agents to execute multi-step GTM workflows such as prospecting, enrichment, CRM updates, and notifications.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: HUBSPOT_ACCESS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 17 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: APOLLO_API_KEY, CLAY_API_KEY, HUBSPOT_ACCESS_TOKEN, SLACK_BOT_TOKEN, SMTP_PASS
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies17 high12 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.7.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.7.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.7.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
🔐 secretAPOLLO_API_KEYApollo → Settings → Integrations → API Keys
🔐 secretCLAY_API_KEYClay → Settings → API
configCLAY_BASE_URLOptional Clay Enterprise API or webhook base URL
configDEMO_MODEtrue lets every tool return realistic mock payloads locally, so someone reviewing the repo can exercise the whole MCP surface without external accounts or paid API access.
🔐 secretHUBSPOT_ACCESS_TOKENHubSpot → Settings → Integrations → Private Apps → Access token
🔐 secretSLACK_BOT_TOKEN[api.slack.com/apps](https://api.slack.com/apps) → OAuth & Permissions → Bot Token (xoxb-…)
configSMTP_HOSTYour mail provider (e.g. smtp.gmail.com)
🔐 secretSMTP_PASSApp password (not your account password)
configSMTP_PORT"": "587",
configSMTP_SECURE
configSMTP_USERYour sending address
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/dylanottinger-gtm-mcp-server-hedexy)](https://m8ven.ai/mcp/dylanottinger-gtm-mcp-server-hedexy)
commit: fce15d46d669b0e78d9487e2ef5e6199148bb60a
code hash: 660f65fb3e66b55916ec98786c4637de745ff873c149e411ec8d3c42711220e7
verified: 7/9/2026, 10:10:50 AM
view raw JSON →