Eclipse Lineage MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
spawn trees, model/config lineage, and version ancestry for agents — who spawned whom, running
Nothing serious here today
Today is the operative word: we check Eclipse Lineage 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 Lineage MCP
same job, measured the same waysigned revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Local test execution and coverage summaries for onboarding agents.
Consent-bound lead work for real-estate agents — provenance on every lead, a Gate on every send, a
Agent identity-continuity chains: signed links across model/config changes, verified offline.
Versioned MongoDB sandboxes for AI agents: branch, time-travel, merge, and undo over MCP.
Governed design-to-print authority for agents — signed provenance from model to machine, safety
MCP server for Sublime Text 4. Lets AI coding agents read and control a running ST instance.
Governed bench access for agents — signed mandates, pinned artifacts, evidence for every session.
Eclipse Lineage MCP — questions
Answers built from our own checks of this server.