Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HubSpot

OCI · GHCR.IO/OHNEBEN/HUBSPOT-MCP:2.0.1 · SCANNED SEP 20

HubSpot API: 1,000+ endpoints as safety-categorized, hub- and plan-aware MCP tools, stdio or HTTP.

40 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1410 tokens (~235/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the HubSpot MCP server?

HubSpot runs locally as a container image, launched with docker run --rm -i ghcr.io/ohneben/hubspot-mcp:2.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/ohneben/hubspot-mcp:2.0.1

# add to Claude Code
claude mcp add ohneben-hubspot-mcp -- docker run --rm -i ghcr.io/ohneben/hubspot-mcp:2.0.1
// .cursor/mcp.json
{
  "mcpServers": {
    "ohneben-hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ohneben-hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ohneben-hubspot-mcp -- docker run --rm -i ghcr.io/ohneben/hubspot-mcp:2.0.1
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ohneben-hubspot-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  ohneben-hubspot-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ohneben/hubspot-mcp:2.0.1"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ohneben-hubspot-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "ohneben-hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Sept 26 40

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed oci/ghcr.io/ohneben/hubspot-mcp:2.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~1,152 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
hubspot_api_request ~234

🔴 ADVANCED · raw HubSpot API request Perform an arbitrary HTTP request against the HubSpot API host — the escape hatch for brand-new or beta endpoints that don't have a dedicated tool (yet). Auth, rate limiting, timeouts and retries are still handled server-side. Host is fixed to https://api.hubapi.com; pass only the path (e.g. "/crm/v3/objects/contacts"). PREFER the dedicated tools: they carry accurate schemas and safety categories. This tool can execute ANY method, including destructive ones — state the method and path clearly and get user confirmation for writes/deletes.

NameTypeReqDescription
bodyOptional request body. Objects are sent as JSON (or as form fields for form content types).
contentTypestringRequest body content type (default application/json).
methodstringyesHTTP method.
pathstringyesAPI path starting with "/", e.g. "/crm/v3/objects/contacts". The host is fixed server-side.
queryobjectOptional query parameters. Array values are repeated (properties=a&properties=b).

No output schema declared.

No examples provided.

hubspot_get_capabilities ~239

🟢 READ-ONLY · HubSpot account access report Reports what THIS HubSpot account and token can use: portal details, granted scopes, daily API usage, and for every API group an access status (available, missing_scopes, blocked, unverified) with the reason, the plan tier HubSpot requires and the scopes that would unlock it. The server already ran this check at startup, probing each paid-tier or beta group with one cheap read, so a plain call returns that result without new API calls. Pass refresh=true after the token's scopes or the portal's subscription changed. probe_groups live-probes further groups, one API call each.

NameTypeReqDescription
include_api_usagebooleanInclude today's API usage vs. the daily limit (private-app tokens only). Default true.
probe_groupsarrayExtra group keys to live-probe with one parameter-free read each (e.g. ["contacts"]). Implies a fresh check. Costs one API call per group.
refreshbooleanRun the check again instead of returning the startup result. Costs one API call per probed group. Default false.

No output schema declared.

No examples provided.

hubspot_get_endpoint ~70

🟢 READ-ONLY · endpoint details Return one endpoint's full description, safety category, plan/scope requirements and JSON input schema. Use the exact tool name from hubspot_search_endpoints.

NameTypeReqDescription
namestringyesEndpoint tool name exactly as returned by hubspot_search_endpoints.

No output schema declared.

No examples provided.

hubspot_graphql_query ~238

🟢 READ-ONLY · query · CRM GraphQL · POST /collector/graphql Run a GraphQL query against HubSpot's CRM data graph and return the JSON result. Fetches records, properties and associations across objects in one round-trip — use it when a REST tool would need several calls or returns too much. HubSpot's GraphQL endpoint supports queries only (no mutations), so this cannot change account data. Endpoint: https://api.hubapi.com/collector/graphql. Plan: Marketing Hub or Content Hub Professional/Enterprise. Scopes: collector.graphql_query.execute. Not available with a HubSpot service key; it needs a private app or OAuth token. Example: {"query": "query { CRM { contact_collection(limit: 3) { items { email firstname associations { company_collection__primary { items { name } } } } } } }"}

NameTypeReqDescription
operationNamestringOptional operation name when the document defines several.
querystringyesThe GraphQL query document (queries only — HubSpot exposes no mutations).
variablesobjectOptional variables object referenced by the query.

No output schema declared.

No examples provided.

hubspot_invoke_endpoint ~113

🟡 WRITE-CAPABLE · invoke a catalog endpoint Call any endpoint in the registry by name with arguments matching its input schema (fetch it first via hubspot_get_endpoint). The registry includes 🟡 write and 🔴 destructive endpoints. Check the endpoint's banner first and confirm with the user before any destructive call (delete / merge / GDPR purge / send).

NameTypeReqDescription
argumentsobjectArguments matching the endpoint's input schema.
namestringyesEndpoint tool name from the catalog.

No output schema declared.

No examples provided.

hubspot_search_endpoints ~258

🟢 READ-ONLY · endpoint catalog search Search this server's catalog of 687 HubSpot endpoint tools by keyword, group, area or safety category. Returns one compact line per tool (name, method+path, category, API; consolidated tools also list the values of their selector argument, e.g. objectType). Each line also says whether this token can use the tool, from the access check the server ran at startup. Workflow: search here → hubspot_get_endpoint for the input schema → hubspot_invoke_endpoint to call it.

NameTypeReqDescription
areastringHubSpot area filter (e.g. "CRM", "CMS", "Marketing").
categorystringSafety-category filter.
groupstringExact group key filter (e.g. "contacts", "marketing-emails").
limitintegerPage size (default 40).
offsetintegerPagination offset (default 0).
querystringKeywords matched against name, path, API name and summary (e.g. "create deal", "hubdb rows").
usable_onlybooleanOnly return tools this token can use according to the startup access check. Default false.

No output schema declared.

No examples provided.

Common questions

What is the HubSpot MCP server?

HubSpot is an MCP server listed in the public MCP registry as io.github.ohneben/hubspot-mcp. HubSpot API: 1,000+ endpoints as safety-categorized, hub- and plan-aware MCP tools, stdio or HTTP. This page covers its container image (ghcr.io/ohneben/hubspot-mcp:2.0.1).

Is the HubSpot MCP server safe to use?

HubSpot scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the HubSpot MCP server expose?

HubSpot exposes 6 tools: hubspot_search_endpoints, hubspot_get_endpoint, hubspot_invoke_endpoint, hubspot_get_capabilities, hubspot_graphql_query, hubspot_api_request. Their descriptions and schemas cost roughly 1,152 tokens of context every time the server is loaded.

Is the HubSpot MCP server still maintained?

HubSpot is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the HubSpot MCP server under?

HubSpot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.