# Eclipse Dispatch MCP (pypi · eclipse-dispatch)

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

- Trust score: 70/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `eclipse-dispatch`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-dispatch/eclipse-dispatch.md), [page](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-dispatch/eclipse-dispatch)

## Channel facts

- Registry: `pypi`
- Package: `eclipse-dispatch`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-dispatch-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 423 tokens (~70/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add cyan-eclipse-technologies-llc-dispatch -- uvx eclipse-dispatch
```

### Cursor

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-dispatch": {
      "command": "uvx",
      "args": [
        "eclipse-dispatch"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyan-eclipse-technologies-llc-dispatch": {
      "command": "uvx",
      "args": [
        "eclipse-dispatch"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cyan-eclipse-technologies-llc-dispatch -- uvx eclipse-dispatch
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyan-eclipse-technologies-llc-dispatch": {
      "type": "local",
      "command": [
        "uvx",
        "eclipse-dispatch"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyan-eclipse-technologies-llc-dispatch --command uvx --arg eclipse-dispatch
```

### Hermes

```yaml
mcp_servers:
  cyan-eclipse-technologies-llc-dispatch:
    command: "uvx"
    args: ["eclipse-dispatch"]
```

### Netclaw

```json
{
  "McpServers": {
    "cyan-eclipse-technologies-llc-dispatch": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "eclipse-dispatch"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyan-eclipse-technologies-llc-dispatch -t stdio -c uvx -a eclipse-dispatch
```

### Other

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-dispatch": {
      "command": "uvx",
      "args": [
        "eclipse-dispatch"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 70, −5)

- [security regression] Source repository: pass → fail

### 2026-10-28 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 60)

First indexed and scored.

## MCP tools (6)

### `draft_create` (~125 tokens)

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.

Input parameters:

- `audience` (string)
- `body` (string, required)
- `canonical_url` (string)
- `draft_id` (string)
- `subtitle` (string)
- `tags` (array)
- `title` (string, required)
- `variants` (object)

### `draft_preview` (~55 tokens)

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).

Input parameters:

- `draft_id` (string, required)

### `draft_approve` (~50 tokens)

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

Input parameters:

- `approved_by` (string)
- `draft_id` (string, required)

### `syndicate_drafts` (~91 tokens)

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.

Input parameters:

- `approval_token` (string, required)
- `draft_id` (string, required)
- `platforms` (array)

### `analytics_report` (~63 tokens)

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.

Input parameters:

- `platforms` (array)

### `receipt_list` (~39 tokens)

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

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-dispatch/eclipse-dispatch#diagnostics

## Score history

- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 75
- 2026-10-27: 60

## 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.

## Links

- PyPI project: https://pypi.org/project/eclipse-dispatch/
- Socket report: https://socket.dev/pypi/package/eclipse-dispatch
- Website: https://eclipsebazaar.com/
- Changelog RSS feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-dispatch/eclipse-dispatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-dispatch/eclipse-dispatch.json
- HTML version of this page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-dispatch/eclipse-dispatch