Developer · Local MCP server
CoReason Ecosystem - Federated MCP Gateway
CoReason Tripartite Architecture Governance Plane. Stateless zero-trust federated MCP gateway.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.CoReason-AI/coreason-ecosystem- Version
- 0.70.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-05-23
- Updated
- 2026-05-23
- Publisher
- CoReason-AI (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/CoReason-AI) · how
- Repository
- github.com/CoReason-AI/coreason-ecosystem
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | coreason-ecosystem | 0.70.3 | stdio |
| OCI image (Docker) | ghcr.io/coreason-ai/coreason-ecosystem:0.70.3 | - | stdio |
How to connect CoReason Ecosystem - Federated MCP Gateway
CoReason Ecosystem - Federated MCP Gateway runs locally from a Python package published to PyPI: coreason-ecosystem version 0.70.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx coreason-ecosystem.
CoReason Ecosystem - Federated MCP Gateway runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/coreason-ai/coreason-ecosystem:0.70.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/coreason-ai/coreason-ecosystem:0.70.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"coreason-ecosystem": {
"command": "uvx",
"args": [
"coreason-ecosystem"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Copilotcliswitchgate MCPRemote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid. | Remote · HTTPLive check: ✗ no handshake |
| Copyright01Copyright deposit API - protect code, text, and websites with Berne Convention proof. | Remote · HTTPLive check: ✗ no handshake |
| Coralquery MCPA paid remote MCP for AI SDK data query MCP, built to return verdicts, receipts, usage logs, and aud. | Remote · HTTPLive check: ✗ no handshake |
| Cordon for MCPCordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals. | Local · stdio |
| CoredashReal User Monitoring for Core Web Vitals. Query LCP, INP, CLS field data from real visitors. | Remote · HTTPLive check: ✓ handshake |
| CorpoleRequirements authority for AI coding agents: binding requirements and acceptance criteria. | Remote · HTTPLive check: ✗ no handshake |
| corpusAI Cloud PricingCloud, GPU and LLM token prices with index fixings. Pay per call over x402 or with a prepaid key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| CorralSearch code and symbols across every clone in your Corral workspace. Zero network calls. | Local · stdio |