Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Eclipse Dispatch MCP

PYPI · ECLIPSE-DISPATCH

Drafts once, syndicates drafts everywhere sanctioned, unifies the analytics. Never publishes

Available components

−5 this week 70 Trust /100

Last scanned (18 hours ago)

Scores higher than 65% of PyPI servers

Category Marketing and SEO

Trust breakdown (7 categories)

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-dispatch-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 Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 423 tokens (~70/item across 6 items; 6 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

Changelog

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 60

    First indexed and scored.

Diagnostics

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-dispatch@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-dispatch-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-dispatch-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.1.0
Rekor log index 3517870774
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:cebfea8c68fe6847d2a20add98d62059c27ed3193db29479ecb816e2bc999767

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 →

MCP tools · 6 exposed · ~423 tokens

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 →

Tool Tokens
analytics_report ~63

D0 unified analytics (read-only): per-platform figures normalized by metric key, each carrying platform provenance + the platform's own definition. Combined figures appear ONLY where definitions are identical; differing definitions are flagged DEFINITIONS_DIFFER, never averaged.

NameTypeReqDescription
platformsarray––

No output schema declared.

No examples provided.

draft_approve ~50

Record owner approval of the current version. Returns an approval token bound to the content hash; any later edit invalidates it.

NameTypeReqDescription
approved_bystring––
draft_idstringyes–

No output schema declared.

No examples provided.

draft_create ~125

Create (or re-version) the canonical draft: title, body, subtitle, canonical_url (home), tags, audience, per-platform variants. Hash-bound: the returned content_hash is what approval binds to. Re-creating an existing draft_id makes a NEW version and resets approval to none.

NameTypeReqDescription
audiencestring––
bodystringyes–
canonical_urlstring––
draft_idstring––
subtitlestring––
tagsarray––
titlestringyes–
variantsobject––

No output schema declared.

No examples provided.

draft_preview ~55

The review artifact: per-platform rendered previews + every adaptation diff against the canonical draft (variant overrides and platform constraints, e.g. Substack = paste pack, beehiiv = draft-only).

NameTypeReqDescription
draft_idstringyes–

No output schema declared.

No examples provided.

receipt_list ~39

List hash-chained receipts (draft creations, approvals, syndications per platform, analytics runs) and verify the chain.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

syndicate_drafts ~91

Fan the approved draft out to per-platform DRAFTS via the fixture adapters (beehiiv/Ghost draft APIs-shaped; Substack gets a paste pack — read-only adapter, never a write). Requires the approval token and an un-invalidated approval hash. There is no publish path.

NameTypeReqDescription
approval_tokenstringyes–
draft_idstringyes–
platformsarray––

No output schema declared.

No examples provided.

Install

How do I install the Eclipse Dispatch MCP server?

Eclipse Dispatch MCP runs locally as a PyPI package, launched with uvx eclipse-dispatch. 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-dispatch

# add to Claude Code
claude mcp add cyan-eclipse-technologies-llc-dispatch -- uvx eclipse-dispatch
Common questions

What is the Eclipse Dispatch MCP server?

Eclipse Dispatch MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/dispatch. Drafts once, syndicates drafts everywhere sanctioned, unifies the analytics. Never publishes. This page covers its PyPI package (eclipse-dispatch).

Is the Eclipse Dispatch MCP server safe to use?

Eclipse Dispatch MCP scores 70 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 Dispatch MCP server expose?

Eclipse Dispatch MCP exposes 6 tools: draft_create, draft_preview, draft_approve, syndicate_drafts, analytics_report, receipt_list. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.

Is the Eclipse Dispatch MCP server still maintained?

Eclipse Dispatch 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 Dispatch MCP server under?

Eclipse Dispatch 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.