Eclipse Muster MCP
PYPI · ECLIPSE-MUSTER
The Customer Graph core: one register of the people an account serves, with provenance on every
Available components
Last scanned (18 hours ago)
Scores higher than 64% of PyPI servers
Category CRM and Sales
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-muster-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 565 tokens (~62/item across 9 items; 9 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_propose" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 29 Oct 26 −5
- Source repository: pass → fail ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 59
First indexed and scored.
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 4 Nov 2026 · Analysed pypi/eclipse-muster@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-muster-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-muster-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.0 |
| Rekor log index | 3518639871 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:580498ee06d71d87bda2adbe1e15ab3eed73e9a2a3c9419a6092ddfd1fff3ec6 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
merge_execute ~79
Execute a proposed graph merge. Requires the owner-confirm token bound to the proposal hash (confirm-merge-<proposal_id>-<hash12>). Graph nodes only — never merges records inside a platform. The pre-merge snapshot is stored on the merge record for unmerge.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | yes | – |
| proposal_id | string | yes | – |
No output schema declared.
No examples provided.
merge_propose ~67
PROPOSE an identity merge between two same-kind records. Returns evidence (matching keys by hash, conflicts) + a proposal hash. Executes nothing (Beacon propose-only doctrine).
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | – | – |
| record_a | string | yes | – |
| record_b | string | yes | – |
No output schema declared.
No examples provided.
merge_unmerge ~51
Undo a confirmed merge from its receipt snapshot, restoring the pre-merge nodes exactly. Requires confirm-unmerge-<merge_id>.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | yes | – |
| merge_id | string | yes | – |
No output schema declared.
No examples provided.
policy_show ~25
Show the tier floors, effective tiers, kill switches, and masking rules in force.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
receipt_list ~40
List the append-only, hash-chained receipts and verify the chain. Receipts carry IDs + hashes only — never content.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
record_ingest ~111
Ingest a canonical Customer Graph record (person / company / deal / ticket / conversation / activity). Every field must carry provenance; a Data Rights Ledger block is required. Customer-authored conversation text is tagged untrusted and instruction-shaped content is quarantined at ingest.
| Name | Type | Req | Description |
|---|---|---|---|
| data_rights | object | – | – |
| external_ids | object | – | – |
| field_provenance | object | – | – |
| fields | object | yes | – |
| kind | string | yes | – |
| record_id | string | – | – |
No output schema declared.
No examples provided.
record_read ~61
Read one graph record with egress masking applied (surface: owner = full email, analytic = domain-only email; phone always partial; gov/payment/health fields null). Receipted.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | – |
| surface | string | – | – |
No output schema declared.
No examples provided.
record_search ~52
Search graph records by kind + substring; returns masked summaries. The query itself is receipted by hash only.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| query | string | – | – |
| surface | string | – | – |
No output schema declared.
No examples provided.
reply_draft ~79
Draft a ticket reply ONLY from record facts, with a citation list. Untraceable facts become MISSING_FACT markers. Customer text is never a fact source; quarantined (instruction-shaped) messages are reported, never obeyed.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | – | – |
| person_id | string | – | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Eclipse Muster MCP server?
Eclipse Muster MCP runs locally as a PyPI package, launched with uvx eclipse-muster. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · eclipse-muster
claude mcp add cyan-eclipse-technologies-llc-muster -- uvx eclipse-muster
What is the Eclipse Muster MCP server?
Eclipse Muster MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/muster. The Customer Graph core: one register of the people an account serves, with provenance on every. This page covers its PyPI package (eclipse-muster).
Is the Eclipse Muster MCP server safe to use?
Eclipse Muster MCP scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Eclipse Muster MCP server expose?
Eclipse Muster MCP exposes 9 tools: record_ingest, record_read, record_search, merge_propose, merge_execute, and 4 more. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Is the Eclipse Muster MCP server still maintained?
Eclipse Muster MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Eclipse Muster MCP server under?
Eclipse Muster MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.