Eclipse Constellation MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 375 installs a week from pypi. Last commit 27 Oct 2026.
The governed, vendor-neutral VM fleet layer for agents: one policy, one receipt ledger, every cloud
Nothing serious here today
Today is the operative word: we check Eclipse Constellation MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add constellation -- uvx eclipse-constellation{
"mcpServers": {
"constellation": {
"command": "uvx",
"args": [
"eclipse-constellation"
]
}
}
}[mcp_servers.constellation]
command = "uvx"
args = ["eclipse-constellation"]{
"mcpServers": {
"constellation": {
"command": "uvx",
"args": [
"eclipse-constellation"
]
}
}
}{
"servers": {
"constellation": {
"type": "stdio",
"command": "uvx",
"args": [
"eclipse-constellation"
]
}
}
}Alternatives to Eclipse Constellation MCP
same job, measured the same wayThe governed database layer for agents — every store in one look, under policy: read-only by
Consent-bound lead work for real-estate agents — provenance on every lead, a Gate on every send, a
Governance layer for agentic AI — signed, verifiable receipts for every agent action.
Local MCP runtime for policy-governed, verified agent actions with durable receipts.
Governed MCP gateway: policy gate on every tool call, hash-chained DSSE receipt on every result.
The governed Zendesk server: OAuth-first, drafts until approved, and a receipt for every touch.
One verification call for third-party agent cards and payment mandates — a receipted verdict a
signed revocation lists for agent cards, keys, and mandates — one feed, every registry, revocation
Eclipse Constellation MCP — questions
Answers built from our own checks of this server.