
Eclipse Envoy MCP
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.0Updated Oct 27, 2026
The signed front door for agent-to-agent business: vetted in, tier-told, drafted — never bound
Overview
A local stdio MCP server described as a signed front door for agent-to-agent business, vetting and tiering incoming agents and drafting replies without binding.
- What you can do
- The listing gives no tool list, instructions or README, so concrete capabilities cannot be confirmed.
- The registry description frames it as a signed entry point for agent-to-agent business interactions.
- It is said to vet incoming agents, assign them a tier, and draft responses rather than commit to them.
- No packages, environment variables or headers are declared, so setup details are unknown.
- When to use it
- Only consider it if you want an assistant to act as a gatekeeper for business exchanges between agents, with incoming agents screened and replies drafted for review. Because no tools or documentation are published, verify what it actually does before relying on it.
- Requirements
- Runs as a local process on the user's machine over stdio, desktop only, with no web executable. No packages, environment variables, headers or authentication are declared, so the runtime and any credentials it needs are undocumented.
Installation
In SourceWeft
- Open Eclipse Envoy MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v0.1.0LatestOct 26, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.