Eclipse Span MCP
Delegation-chain governance: spawn limits, depth caps, mandate attenuation
status: in-developmentclass: mcpDelegation & Multi-Agent Governance
Vendor: Cyan Eclipse Technologies
What it does
- Delegation-chain keeper for agent spawns: root mandate refs, chain links, spawn records, ancestry, subtree, and effective-mandate queries
- Every proposed spawn is checked against a total componentwise attenuation order — six mandate components plus max_children, max_subtree, and spawn_rate budgets — and every amplification refuses by name
- Subtree budgets are enforced at every ancestor, making chain-laundering by splitting spawns across children arithmetically impossible
- Effective mandate is computed as the componentwise path minimum, never stored; presented chains must walk to an owner-signed root or land CHAIN_UNVERIFIED
- Unchecked spawns are flagged UNCHECKED_SPAWN and reported, never hidden. Span issues no mandates, dispatches nothing, and has no override verb. v0 posture is check-and-record, not blocking enforcement in external frameworks
Tools
root_register · root_revoke · budget_set · chain_view · node_effective_mandate · spawn_check · spawn_record · spawn_close · chain_verify · ancestry · subtree
Platforms
- MCP over stdio (HTTP transport on roadmap)
Certification
Bench verdict: CERTIFIED(local)
Certified scope: CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-26, 23 pass, 1 na of 24 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/span.py. Run 5 is the standing card; runs 1–4 FAILED cards are retained append-only. N-CHECK: NOVELTY_PROVEN — a proposed spawn is checked against a total componentwise attenuation order walked to an owner-signed root, with subtree budgets enforced at every ancestor.
Not tested:
- Blocking enforcement inside external frameworks — gated on framework hook availability per framework (spec §5.5); v0 claims check-and-record only, NOT a blocking gate.
- Cross-organization chains — gated on Envoy counterparty vetting tiers; v0 verifies foreign chains as evidence only (T1 verdict on presented artifacts), never registers foreign roots as trusted.
- Production signing-key custody — v0 signs with a local seed key (keys/, gitignored, chmod 600); custody is a gated decision.
- Hosted / multi-tenant operation and auth beyond the stdio process boundary.
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-span-mcp-2026-10-26-5.json
Pricing
Free local v0.1; suite pricing TBD per spec
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-span-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).