Eclipse Crosslist MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
Publish once, tracked everywhere: registry-native facets plus a mandate-bound listing ledger.
Nothing serious here today
Today is the operative word: we check Eclipse Crosslist 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 Crosslist MCP
same job, measured the same waysigned revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Consent-bound lead work for real-estate agents — provenance on every lead, a Gate on every send, a
Drafts once, syndicates drafts everywhere sanctioned, unifies the analytics. Never publishes
One canonical, hash-bound package behind every Eclipse social adapter. It publishes nothing itself
MCP-native hosting: publish and operate AI-built web apps live at name.percher.run.
Every Xero Accounting read plus a local SQLite ledger - aging, reconciliation, and GL tie-out
The Consent Registry and Number Registry every Eclipse telephony adapter obeys.
Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.
Eclipse Crosslist MCP — questions
Answers built from our own checks of this server.