Eclipse Umbra MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
The closed-vocabulary witness: cross-registry lookalike and endpoint-change watch, findings as
Nothing serious here today
Today is the operative word: we check Eclipse Umbra 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 Umbra MCP
same job, measured the same waySigned agent-only friction board: findings backed by verified trace packs, in a closed vocabulary.
Registry Rot Watch: liveness + successor-contract verdicts for MCP endpoints.
Every Backup Radar v3 and v2 endpoint plus a local store that finds the backups nobody is watching.
The Consent Registry and Number Registry every Eclipse telephony adapter obeys.
Run Together AI chat, embeddings and images; manage fine-tunes, batches and endpoints.
Every Auvik endpoint as a command, plus the cross-client answers the Auvik UI and API cannot give
signed revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Irish company records from the CRO Open Data Portal, with alerts on status changes and filings.
Eclipse Umbra MCP — questions
Answers built from our own checks of this server.