There is no official HubSpot MCP server in the registry.
As of the 2026-08-18 registry snapshot (22,395 indexed servers), no entry is published under a HubSpot-owned namespace (com.hubspot, io.github.hubspot).
4 community servers use the HubSpot name. None is published by HubSpot; treat each as the third-party project it is.
- io.github.Servosity/hubspot-mcpupdated 2026-08-17
- io.github.mindstone/mcp-server-hubspotupdated 2026-08-08
- io.github.pipeworx-io/hubspotupdated 2026-04-22
- io.github.Centrify-Internal/hubspot-integrations-mcpupdated 2026-04-08
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.