Is mcp-gateway-registry safe to use?

mcp-gateway-registry has an HVTrust score of 61.0/100 (Grade C), ranked #671 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for mcp-gateway-registry?

mcp-gateway-registry scores 61.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.0k GitHub stars and is categorized under Protocols & Tool Integration.

mcp-gateway-registry

Repository

Website

Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI agents and AI coding assistants. Transform scattered MCP server chaos into governed, auditable tool access with…

Protocols & Tool Integration Python Listed Apache-2.0

Is mcp-gateway-registry safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 0%

Last push yesterday

Compare mcp-gateway-registry

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Suggest a correction

In detail: mcp-gateway-registry scores 61.0/100 (Grade C), ranked #671 of 1374 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 6.2/10; recent commits are unsigned; last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How mcp-gateway-registry 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.

Raise the OSSF Scorecard from 6.2 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +5.7 → 66.7 B · #25 of 63
Sign every commit0% signed today +5.0 → 66.0 B · #28 of 63

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships mcp-gateway-registry 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.

Source Unsigned

github.com/agentic-community/mcp-gateway-registry, Apache-2.0, last pushed 2026-11-04. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies6
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 8

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. mcp-gateway-registry is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-26 OSSF Scorecard: 6.9/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 mcp-gateway-registry’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 mcp-gateway-registry compares in Protocols & Tool Integration

#38 Agent Reach 62.5 +1.5
#39 CodeGraph 62.4 +1.4
#40 mcp-gateway-registry 61.0 this agent
#41 open-connector 60.5 −0.5
#42 MCP Client for Ollama 58.7 −2.3

Bars show each HVTrust score; the tick marks mcp-gateway-registry’s 61.0.

Where the 61.0 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

61.0 / 100 · 100.0% confidence

mcp-gateway-registry Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.8 / 25

3.3 below avg 11.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

0.8 above avg 13.0

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

5.4 above avg 14.5

AdoptionLog-scaled stars · package downloads

7.2 / 20

3.9 below avg 11.1

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-24

Rank Moved

Rank dropped 25 spots (#656 → #681)

2026-10-22

Provider Removed

Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)

2026-10-22

Rank Moved

Rank rose 13 spots (#670 → #657)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/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.

Compare with another agent View Protocols & Tool Integration Report missing data

79.3

Activity sub-score · out of 100

#40

In Protocols & Tool Integration

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars

1.0k

Forks

259

Last Push

2026-11-04

yesterday

Commits (4 wk)

172

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

105

Rank Change

▲1

was #672

Analysis

Activity Inputs

79.3 / 100

StarsRepository reach

18.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.2 / 20

Common questions about mcp-gateway-registry

mcp-gateway-registry has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does mcp-gateway-registry publish package provenance?

No published build provenance is currently detected for mcp-gateway-registry. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does mcp-gateway-registry have an OpenSSF Scorecard?

mcp-gateway-registry has an OpenSSF Scorecard score of 6.2/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 mcp-gateway-registry actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does mcp-gateway-registry use?

mcp-gateway-registry ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are mcp-gateway-registry's commits signed?

0% of the last 100 commits to mcp-gateway-registry 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

mcp-gateway-registry appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

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 mcp-gateway-registry'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-10-22

Provider Removed

Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Multi-provider (LiteLLM)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain mcp-gateway-registry?

For maintainers

HVTrust scores mcp-gateway-registry 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

2026-10-24

Rank Moved

Rank dropped 25 spots (#656 → #681)

2026-10-22

Provider Removed

Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)

2026-10-22

Rank Moved

Rank rose 13 spots (#670 → #657)

2026-10-09

Rank Moved

Rank dropped 11 spots (#640 → #651)

2026-10-04

Rank Moved

Rank dropped 32 spots (#599 → #631)

2026-10-01

Rank Moved

Rank rose 11 spots (#599 → #588)

2026-09-25

Rank Moved

Rank dropped 20 spots (#572 → #592)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Multi-provider (LiteLLM)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 253 spots (#318 → #571)

2026-09-23

HVTrust Changed

HVTrust up 9.5pts (52.4 → 61.9)

2026-09-22

Newly Listed

First tracked at rank #318

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 15 spots (#574 → #559)

2026-09-12

Rank Moved

Rank dropped 29 spots (#533 → #562)

2026-09-08

Rank Moved

Rank dropped 27 spots (#500 → #527)

2026-09-07

Rank Moved

Rank dropped 19 spots (#481 → #500)

2026-09-05

Rank Moved

Rank dropped 74 spots (#400 → #474)

2026-09-03

Rank Moved

Rank dropped 25 spots (#371 → #396)

2026-09-02

Rank Moved

Rank dropped 11 spots (#360 → #371)

2026-09-01

Rank Moved

Rank dropped 18 spots (#342 → #360)

2026-08-31

Rank Moved

Rank dropped 26 spots (#316 → #342)

2026-08-30

Rank Moved

Rank rose 10 spots (#326 → #316)

2026-08-29

Rank Moved

Rank dropped 11 spots (#315 → #326)

2026-08-26

Scorecard Added

OSSF Scorecard: 6.9/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 538 spots (#845 → #307)

2026-08-26

HVTrust Changed

HVTrust up 38.1pts (24.8 → 62.9)

2026-08-16

Rank Moved

Rank dropped 15 spots (#823 → #838)

2026-08-13

Rank Moved

Rank rose 29 spots (#856 → #827)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank dropped 19 spots (#837 → #856)

2026-08-10

Rank Moved

Rank dropped 46 spots (#792 → #838)

2026-08-08

Rank Moved

Rank dropped 334 spots (#438 → #772)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-gateway-registry.svg)](https://hvtracker.net/agents/mcp-gateway-registry)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-gateway-registry"><img src="https://hvtracker.net/badge/mcp-gateway-registry.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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

mcp-gateway-registry

How mcp-gateway-registry could raise its score

Chain of custody

Source Unsigned

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How mcp-gateway-registry compares in Protocols & Tool Integration

Where the 61.0 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about mcp-gateway-registry

AI agent surface

Maintain mcp-gateway-registry?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Protocols & Tool Integration