Eclipse Orbit MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 27, 2026

The HubSpot wrap: the vendor's server, under policy — classified tools, approval gates, masking

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

A local desktop MCP server that wraps HubSpot access under policy, with classified tools, approval gates and data masking.

What you can do
  • The listing gives no tool list, so capabilities are known only from the short description.
  • It presents itself as a policy layer around the vendor's HubSpot server, exposing HubSpot actions as classified tools.
  • It adds approval gates, so some actions are meant to require sign-off before running.
  • It applies masking, presumably to sensitive values returned by those tools.
When to use it
Consider it if you want an assistant to work with HubSpot data but need a policy layer in front of the vendor's server, with tool classification, approval steps and masking rather than direct access.
Requirements
Runs as a local process on the user's machine over stdio, desktop only. No packages, environment variables, headers or authentication are declared, so how it reaches HubSpot and what it needs to do so is not stated.
Before you install
HubSpot data is customer and business data; masking and approval gates are claimed but not documented here, so verify what is actually masked and which actions are gated. No credentials or setup are declared, so confirm how it authenticates to HubSpot before use. The tool list is unavailable, so the exact actions it can take are unknown.

Installation

In SourceWeft

  1. Open Eclipse Orbit MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 26, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.