Eclipse Span MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
Delegation-chain governance: spawn limits, depth caps, mandate attenuation
Nothing serious here today
Today is the operative word: we check Eclipse Span MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Eclipse Span MCP
same job, measured the same wayTeam-chat agent governance — the signed mandate, verified disclosure, review-first posting and
Runaway enforcement — spawn, loop, and spend-velocity detection with automatic mandate freeze.
Eclipse Airtime — mandate-bound ad operations.
Ed25519-signed MCP tool manifests + spawn attestation. Layer-2 supply-chain hardening.
Signed Agent Cards, policy-gated delegation, certification before hire.
signed revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Governed bench access for agents — signed mandates, pinned artifacts, evidence for every session.
spawn trees, model/config lineage, and version ancestry for agents — who spawned whom, running
Eclipse Span MCP — questions
Answers built from our own checks of this server.