Hubspot Marketing (npm) MCP Server

hubspot-marketing-mcp npm v1.0.0

Published by zleventer — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for HubSpot CRM — 33 tools covering contacts, companies, deals, pipelines, lists, emails, forms, workflows, and properties

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • hs_contact_by_emailno sensitive capability
  • hs_create_contactno sensitive capability
  • hs_crm_searchno sensitive capability
  • hs_deals_by_stageno sensitive capability
  • hs_form_submissionsno sensitive capability
  • hs_get_companyno sensitive capability
  • hs_get_contactno sensitive capability
  • hs_get_dealno sensitive capability
  • hs_get_email_campaign_statsno sensitive capability
  • hs_get_formno sensitive capability
Show 20 more tools ↓
  • hs_get_listno sensitive capability
  • hs_get_propertyno sensitive capability
  • hs_get_workflowno sensitive capability
  • hs_list_company_contactsno sensitive capability
  • hs_list_email_campaignsno sensitive capability
  • hs_list_formsno sensitive capability
  • hs_list_listsno sensitive capability
  • hs_list_marketing_emailsno sensitive capability
  • hs_list_membersno sensitive capability
  • hs_list_ownersno sensitive capability
  • hs_list_pipelinesno sensitive capability
  • hs_list_propertiesno sensitive capability
  • hs_list_workflowsno sensitive capability
  • hs_pipeline_summaryno sensitive capability
  • hs_recent_contactsno sensitive capability
  • hs_recent_dealsno sensitive capability
  • hs_search_companiesno sensitive capability
  • hs_search_contactsno sensitive capability
  • hs_search_dealsno sensitive capability
  • hs_update_contactno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 99/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/hubspot-marketing-mcp/badge.svg)](https://mcptrustchecker.com/registry/hubspot-marketing-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/hubspot-marketing-mcp"><img src="https://mcptrustchecker.com/registry/hubspot-marketing-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/hubspot-marketing-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan hubspot-marketing-mcp --online

Use the free API → How scoring works

Other implementations of Hubspot Marketing 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Business & CRM