
CoReason Ecosystem — Federated MCP Gateway
io.github.CoReason-AIPublished by GitHub account CoReason-AIv0.70.3Updated Oct 24, 2026
CoReason Tripartite Architecture Governance Plane. Stateless zero-trust federated MCP gateway.
Overview
A local, stateless federated MCP gateway from the CoReason tripartite architecture, positioned as a governance plane for connecting assistants to other MCP tool
- What you can do
- Acts as a federated MCP gateway, presenting itself as a single local entry point through which an assistant reaches other MCP servers rather than one server at a time. Described as a governance plane within the CoReason tripartite architecture, so it is framed around governing and brokering tool access. Described as stateless and zero-trust, meaning it keeps no session state and does not implicitly trust connected services. No individual tools are listed, so the concrete operations available are not documented in the supplied material.
- When to use it
- Consider it when you want one governed gateway in front of several MCP servers instead of configuring each one separately, or when a zero-trust, stateless brokering layer is a requirement. Because no tools or usage documentation are provided, it is hard to judge fit without checking the project's own documentation first.
- Requirements
- Runs as a local process over stdio, distributed as a PyPI package or an OCI container image, so a local Python or container runtime is needed. It is desktop-only and not web-executable. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open CoReason Ecosystem — Federated MCP Gateway 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.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.70.3LatestSep 16, 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.