updated 2026-10-16 16:07 UTC

Cortex Gateway

Repository

Federated MCP gateway: one OAuth 2.1-protected, spec-compliant MCP server in front of all your apps. Backends stay plain HTTP (~120-line contract) or proxied native MCP servers with a per-user token vault. Scope-filtered tools, live discovery, audit trail. Give agents curated, governed access to…

MCP Servers HTML Listed MIT

Is Cortex Gateway safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10
Provenance None
Signed commits 0%
Last push 55d ago
Compare Cortex Gateway

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Cortex Gateway scores 39.7/100 (Grade D), ranked #1218 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; recent commits are unsigned; last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cortex Gateway could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Cortex Gateway and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/wellknownmcp/cortex-gateway, MIT, last pushed 2026-08-22. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    Distributed as the container image ghcr.io/wellknownmcp/cortex-gateway:v0.2.0; HVTracker doesn't check that registry's source link yet.

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 3.2/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Cortex Gateway’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Cortex Gateway compares in MCP Servers

  1. #700 Pagecast 40.0 +0.3
  2. #701 Power Automate MCP Server by Flow Studio 39.9 +0.2
  3. #702 Cortex Gateway 39.7 this agent
  4. #703 Gate DEX MCP 39.6 −0.1
  5. #704 MCP Server Code Runner 39.6 −0.1

Bars show each HVTrust score; the tick marks Cortex Gateway’s 39.7.

Where the 39.7 comes from

HVTrust dimensions vs the MCP Servers average

39.7 / 100 · 100.0% confidence

Cortex Gateway MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
5.5 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
8.3 / 20
4.0 below avg 12.3
AdoptionLog-scaled stars · package downloads
2.7 / 20
4.7 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 10 spots (#1205 → #1215)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1172 → #1183)
2026-10-08
Rank Moved
Rank rose 31 spots (#1203 → #1172)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 55 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Cortex Gateway View MCP Servers Report missing data
24.2
Activity sub-score · out of 100
#702
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 55 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
12
Forks
0
Last Push
2026-08-22
55 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼3
was #1215

Analysis

Activity Inputs

24.2 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
17.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
0.0 / 20

Common questions about Cortex Gateway

Public trust evidence for Cortex Gateway is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Cortex Gateway publish package provenance?
No published build provenance is currently detected for Cortex Gateway. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cortex Gateway have an OpenSSF Scorecard?
Cortex Gateway has an OpenSSF Scorecard score of 4.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Cortex Gateway actively maintained?
Slowing down. Last push was 55 days ago — keep an eye on whether activity resumes.
What license does Cortex Gateway use?
Cortex Gateway ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cortex Gateway's commits signed?
0% of the last 100 commits to Cortex Gateway are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Cortex Gateway appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Cortex Gateway's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Cortex Gateway?

For maintainers

HVTrust scores Cortex Gateway from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 29HVTrust 6Listed 2Score 1Scorecard 1Delisted 1MCP 1Surface 1
2026-10-15
Rank Moved
Rank dropped 10 spots (#1205 → #1215)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1172 → #1183)
2026-10-08
Rank Moved
Rank rose 31 spots (#1203 → #1172)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
HVTrust Changed
HVTrust up 19.5pts (20.1 → 39.6)
2026-09-22
Newly Listed
First tracked at rank #1176
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank rose 171 spots (#1297 → #1126)
2026-09-17
HVTrust Changed
HVTrust up 13.6pts (28.3 → 41.9)
2026-09-16
Rank Moved
Rank dropped 199 spots (#1098 → #1297)
2026-09-16
HVTrust Changed
HVTrust down 14.9pts (43.2 → 28.3)
2026-09-15
Rank Moved
Rank dropped 32 spots (#1066 → #1098)
2026-09-12
Rank Moved
Rank dropped 11 spots (#1054 → #1065)
2026-09-09
Rank Moved
Rank dropped 18 spots (#1028 → #1046)
2026-09-08
Rank Moved
Rank rose 236 spots (#1264 → #1028)
2026-09-08
HVTrust Changed
HVTrust up 14.6pts (30.3 → 44.9)
2026-09-07
Rank Moved
Rank dropped 281 spots (#983 → #1264)
2026-09-07
HVTrust Changed
HVTrust down 14.7pts (45.0 → 30.3)
2026-09-06
Rank Moved
Rank dropped 15 spots (#968 → #983)
2026-09-05
Scorecard Added
OSSF Scorecard: 3.2/10
2026-09-05
Rank Moved
Rank rose 326 spots (#1294 → #968)
2026-09-05
HVTrust Changed
HVTrust up 25.4pts (19.7 → 45.1)
2026-09-03
Rank Moved
Rank dropped 13 spots (#1274 → #1287)
2026-09-02
Rank Moved
Rank dropped 20 spots (#1254 → #1274)
2026-09-01
Rank Moved
Rank dropped 18 spots (#1236 → #1254)
2026-08-31
Rank Moved
Rank dropped 21 spots (#1215 → #1236)
2026-08-30
Rank Moved
Rank dropped 18 spots (#1197 → #1215)
2026-08-29
Rank Moved
Rank dropped 26 spots (#1171 → #1197)
2026-08-28
Rank Moved
Rank dropped 17 spots (#1154 → #1171)
2026-08-27
Rank Moved
Rank dropped 15 spots (#1139 → #1154)
2026-08-26
Rank Moved
Rank dropped 59 spots (#1080 → #1139)
2026-08-22
Rank Moved
Rank rose 21 spots (#1093 → #1072)
2026-08-20
Rank Moved
Rank dropped 10 spots (#1085 → #1095)
2026-08-19
Rank Moved
Rank dropped 43 spots (#1042 → #1085)
2026-08-17
Rank Moved
Rank rose 16 spots (#1061 → #1045)
2026-08-16
Rank Moved
Rank rose 35 spots (#1096 → #1061)
2026-08-16
Activity Score Changed
Activity score up 5pts (42 → 48)
2026-08-14
Rank Moved
Rank dropped 15 spots (#1080 → #1095)
2026-08-12
Rank Moved
Rank rose 13 spots (#1086 → #1073)
2026-08-10
Rank Moved
Rank dropped 68 spots (#1013 → #1081)
2026-08-08
Newly Listed
First tracked at rank #1006
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/cortex-gateway.svg)](https://hvtracker.net/agents/cortex-gateway)
HTML:
<a href="https://hvtracker.net/agents/cortex-gateway"><img src="https://hvtracker.net/badge/cortex-gateway.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON