There is no official HubSpot MCP server in the registry.
As of the 2026-11-19 registry snapshot (66,101 indexed servers), no entry is published under a HubSpot-owned namespace (com.hubspot, io.github.hubspot).
8 community servers use the HubSpot name. None is published by HubSpot; treat each as the third-party project it is.
- dev.wirecat/hubspot-cliupdated 2026-11-18
- io.github.mindstone/mcp-server-hubspotupdated 2026-11-16
- io.github.Servosity/hubspot-mcpupdated 2026-11-14
- com.pronovahq/pronova-sales-hubspotupdated 2026-11-11
- io.github.M-Pineapple/hubspot-auditorupdated 2026-11-10
- io.github.pipeworx-io/hubspotupdated 2026-11-02
- io.github.danielpopamd/hubspot-mcpupdated 2026-10-21
- io.github.mrfentmen/hubspot-mcpupdated 2026-10-17
The registry verifies namespace ownership, so a registered vendor entry is the one identity an agent can pin. Without one there is no verified HubSpot namespace, no canonical entry to pin a tool contract against, and no drift history when the tool surface changes. A server using the name may still be useful; it is just not HubSpot speaking.
How mcpindex evaluates what a server declares versus what it does is covered in the methodology and the trust model.
Publishing to the MCP registry gives your users a verifiable namespace. mcpindex syncs the registry daily; a published entry replaces this page with a normal server page, which you can then claim.