Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CoReason Ecosystem — Federated MCP Gateway

OCI · GHCR.IO/COREASON-AI/COREASON-ECOSYSTEM:0.70.3 · 2 COMPONENTS

CoReason Tripartite Architecture Governance Plane. Stateless zero-trust federated MCP gateway.

Available components

oci · ghcr.io/coreason-ai/coreason-ecosystem:0.70.3 12 pypi · coreason-ecosystem 41
0 this week 12 Trust /100

Last scanned (9 hours ago)

Scores higher than 32% of OCI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency58
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to CoReason-AI/coreason-ecosystem). View diagnostics → Pass
  • License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 165 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: CoReason-AI/coreason-ecosystem security
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
  • 26 Jul 26 0

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/coreason-ai/coreason-ecosystem:0.70.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via OCI referrers API
Source repo CoReason-AI/coreason-ecosystem
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/CoReason-AI/coreason-ecosystem/.github/workflows/publish.yml@refs/tags/v0.70.3
Rekor log index 1615070074
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:033c2f8c1df60822f318c4e1a91baa1af0db4dcac3a13b9d510df5daba6fb26f

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the CoReason Ecosystem — Federated MCP Gateway server?

CoReason Ecosystem — Federated MCP Gateway runs locally as a container image, launched with docker run --rm -i ghcr.io/coreason-ai/coreason-ecosystem:0.70.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/coreason-ai/coreason-ecosystem:0.70.3

# add to Claude Code
claude mcp add coreason-ai-coreason-ecosystem -- docker run --rm -i ghcr.io/coreason-ai/coreason-ecosystem:0.70.3
Common questions

What is the CoReason Ecosystem — Federated MCP Gateway server?

CoReason Ecosystem — Federated MCP Gateway is listed in the public MCP registry as io.github.CoReason-AI/coreason-ecosystem. CoReason Tripartite Architecture Governance Plane. Stateless zero-trust federated MCP gateway. This page covers its container image (ghcr.io/coreason-ai/coreason-ecosystem:0.70.3).

Is the CoReason Ecosystem — Federated MCP Gateway server safe to use?

CoReason Ecosystem — Federated MCP Gateway scores 12 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the CoReason Ecosystem — Federated MCP Gateway server still maintained?

CoReason Ecosystem — Federated MCP Gateway is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the CoReason Ecosystem — Federated MCP Gateway server under?

CoReason Ecosystem — Federated MCP Gateway declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.