HubSpot

A community-built HubSpot MCP with the broadest tool coverage in our corpus (112 tools across HubSpot's full CRM surface), but with significant disclosure-versus-reality gaps. The package's PRIVACY.md states telemetry doesn't transmit IP or port; the runtime does. An undeclared HTTP server runs alongside the documented stdio mode that would expose HubSpot credentials if reachable on a network. The production dependency tree carries 17 known vulnerabilities (2 critical, 5 high), and telemetry defaults to 100% sampling with a 5-second export interval. If you need broad HubSpot tool coverage and you can run this in a tightly-controlled environment, the tool surface is real; for environments with privacy, compliance, or supply-chain attestation requirements, this MCP doesn't currently meet the bar.

A Python-based HubSpot MCP that adds vector storage and persistent local caching of CRM data on top of HubSpot's API — features marketed as "context retention" for AI assistants. The headline concern is that the local cache is full plaintext JSON of HubSpot record content, with no encryption, a 7-day rolling window, and no documented retention policy. CLI-flag credential exposure in the host process list, an exact-pinned dependency with known CVEs, and tool-count discrepancies (16 tools registered, 7 documented) round out the concerns. If your organization has data residency requirements, encryption-at-rest mandates, or audit constraints on CRM data, this MCP places that data outside the control plane you've reasoned about.

A multi-tenant HubSpot MCP that markets credential persistence as the headline feature — store keys for multiple HubSpot accounts in your OS keychain, switch between them at runtime. The architecture works as advertised, but every disclosure layer around it is thin: no public source repo despite shipping the source code in the package, no SECURITY.md, no PRIVACY.md, ten months of stagnation since the last release, internal AI-orchestration documents accidentally shipped in the npm tarball, and the same architectural template recurs across at least six of this publisher's MCPs spanning different vendors. If you specifically need multi-account credential management for HubSpot, the feature works as advertised — but 10 months of stagnation with no security policy means nobody is watching for issues in the code that holds your credentials.