# HubSpot (oci · ghcr.io/ohneben/hubspot-mcp:2.0.1)

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

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/ohneben/hubspot-mcp:2.0.1`: 40/100 (this document), [markdown](https://verifymcp.io/servers/ohneben-hubspot-mcp/ghcr-io-ohneben-hubspot-mcp-2-0-1.md), [page](https://verifymcp.io/servers/ohneben-hubspot-mcp/ghcr-io-ohneben-hubspot-mcp-2-0-1)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/ohneben/hubspot-mcp:2.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

### Claude

```bash
claude mcp add ohneben-hubspot-mcp -- docker run --rm -i ghcr.io/ohneben/hubspot-mcp:2.0.1
```

### Cursor

```json
{
  "mcpServers": {
    "ohneben-hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ohneben-hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
```

### Codex

```bash
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

```yaml
mcp_servers:
  ohneben-hubspot-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ohneben/hubspot-mcp:2.0.1"]
```

### Netclaw

```json
{
  "McpServers": {
    "ohneben-hubspot-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "ohneben-hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-15 (score 40)

First indexed and scored.

## MCP tools (6)

### `hubspot_search_endpoints` (~258 tokens)

🟢 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.

Input parameters:

- `area` (string): HubSpot area filter (e.g. "CRM", "CMS", "Marketing").
- `category` (string): Safety-category filter.
- `group` (string): Exact group key filter (e.g. "contacts", "marketing-emails").
- `limit` (integer): Page size (default 40).
- `offset` (integer): Pagination offset (default 0).
- `query` (string): Keywords matched against name, path, API name and summary (e.g. "create deal", "hubdb rows").
- `usable_only` (boolean): Only return tools this token can use according to the startup access check. Default false.

### `hubspot_get_endpoint` (~70 tokens)

🟢 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.

Input parameters:

- `name` (string, required): Endpoint tool name exactly as returned by hubspot_search_endpoints.

### `hubspot_invoke_endpoint` (~113 tokens)

🟡 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).

Input parameters:

- `arguments` (object): Arguments matching the endpoint's input schema.
- `name` (string, required): Endpoint tool name from the catalog.

### `hubspot_get_capabilities` (~239 tokens)

🟢 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.

Input parameters:

- `include_api_usage` (boolean): Include today's API usage vs. the daily limit (private-app tokens only). Default true.
- `probe_groups` (array): Extra group keys to live-probe with one parameter-free read each (e.g. ["contacts"]). Implies a fresh check. Costs one API call per group.
- `refresh` (boolean): Run the check again instead of returning the startup result. Costs one API call per probed group. Default false.

### `hubspot_graphql_query` (~238 tokens)

🟢 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 } } } } } } }"}

Input parameters:

- `operationName` (string): Optional operation name when the document defines several.
- `query` (string, required): The GraphQL query document (queries only — HubSpot exposes no mutations).
- `variables` (object): Optional variables object referenced by the query.

### `hubspot_api_request` (~234 tokens)

🔴 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.

Input parameters:

- `body`: Optional request body. Objects are sent as JSON (or as form fields for form content types).
- `contentType` (string): Request body content type (default application/json).
- `method` (string, required): HTTP method.
- `path` (string, required): API path starting with "/", e.g. "/crm/v3/objects/contacts". The host is fixed server-side.
- `query` (object): Optional query parameters. Array values are repeated (properties=a&properties=b).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ohneben-hubspot-mcp/ghcr-io-ohneben-hubspot-mcp-2-0-1#diagnostics

## Score history

- 2026-09-20: 40
- 2026-09-19: 40
- 2026-09-18: 40
- 2026-09-17: 40
- 2026-09-16: 40
- 2026-09-15: 40

## 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.

## Links

- Repository: https://github.com/ohneben/Hubspot-MCP
- Changelog RSS feed: https://verifymcp.io/servers/ohneben-hubspot-mcp/ghcr-io-ohneben-hubspot-mcp-2-0-1.xml
- Changelog JSON feed: https://verifymcp.io/servers/ohneben-hubspot-mcp/ghcr-io-ohneben-hubspot-mcp-2-0-1.json
- HTML version of this page: https://verifymcp.io/servers/ohneben-hubspot-mcp/ghcr-io-ohneben-hubspot-mcp-2-0-1
