
Eclipse Orbit MCP
The HubSpot wrap: the vendor's server, under policy — classified tools, approval gates, masking, and receipts.
status: in-developmentclass: mcpCRM / Customer Service Infrastructure
Vendor: Cyan Eclipse Technologies
What it does
- Governing proxy (the Eclipse WRAP posture) in front of HubSpot's official MCP server: policy, approval gates, masking, and receipts around the vendor's tools
- Pinned classification registry: unclassified vendor tools are invisible to clients; vendor T3 tools (delete, bulk) are classified but never surfaced in v1
- Drift defense: if a vendor tool's tier rises under the wrap, the proxy halts it and emits a notice receipt until an owner clears the halt by name
- T2 calls (ticket reply send, deal stage move) require approval tokens bound to the tool plus the exact arguments hash
- HubSpot custom objects are a declared OBJECT_GAP on every inventory view — absent from the vendor tool set and never reached around
Tools
vendor_tools · vendor_refresh · vendor_call · halt_clear · receipt_list
Platforms
- MCP over stdio
Certification
Bench verdict: CERTIFIED(simulator)
Certified scope: CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, 16/17 checks pass, 1 na (U1 auth: local stub vendor, no live credential). Run by W-003 (Verity), suites/orbit.py.
Not tested:
- The real HubSpot MCP server (mcp.hubspot.com) — C0's vendor is a local stub shaped like its tool surface; the live wrap is C1 against an owner account (spec 11.5).
- Real OAuth 2.1 + PKCE connector flow and per-portal scope lists — recorded at live connection, not in C0.
- Free-tier tool parity of the vendor server — flagged [verify] in the spec for C1.
- Custom objects — declared OBJECT_GAP (absent from the vendor tool set); not reachable through Orbit by design (spec 11.4).
- Vendor drift against the REAL vendor inventory cadence — the drift rules are proven against stub fixtures (tier rise, added tool).
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-orbit-mcp-2026-10-25.json
Pricing
Free local v0.1; family pricing TBD per spec
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-orbit-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).