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.

MCP Zero-Trust Gateway

PYPI · MCP-ZTGATEWAY

Security gateway: verifies what MCP servers really do, then confines each call. Needs Docker.

Available components

+15 this week 38 Trust /100

Last scanned (20 hours ago)

Scores higher than 30% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Build provenance not yet verified. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 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: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
  • Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 4 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.

What we tested

Checks we ran (8)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • License
  • Maintenance
  • MCP protocol

Checks we could not complete (6)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Provenance in Provenance & TransparencyBuild provenance not yet verified.
  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 38

    First indexed and scored.

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 21 Nov 2026 · Analysed pypi/mcp-ztgateway@0.5.5

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem pypi
Reason Unsupported forge
Discovered via Registry attestation endpoint

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 34 packages
Packages resolved 34
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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 →

The sandbox run completed and this package exposed no tools.

Install

How do I install the MCP Zero-Trust Gateway server?

MCP Zero-Trust Gateway runs locally as a PyPI package, launched with uvx mcp-ztgateway stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-ztgateway

# add to Claude Code
claude mcp add nabrahma-mcp-ztgateway -- uvx mcp-ztgateway stdio
Common questions

What is the MCP Zero-Trust Gateway server?

MCP Zero-Trust Gateway is listed in the public MCP registry as io.github.nabrahma/mcp-ztgateway. Security gateway: verifies what MCP servers really do, then confines each call. Needs Docker. This page covers its PyPI package (mcp-ztgateway).

Is the MCP Zero-Trust Gateway server safe to use?

MCP Zero-Trust Gateway scores 38 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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.

What tools does the MCP Zero-Trust Gateway server expose?

MCP Zero-Trust Gateway exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the MCP Zero-Trust Gateway server still maintained?

MCP Zero-Trust Gateway is still listed as active in the MCP registry. We last reached this channel on 21 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 MCP Zero-Trust Gateway server under?

MCP Zero-Trust Gateway declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the MCP Zero-Trust Gateway server?

VerifyMCP ran 8 checks on MCP Zero-Trust Gateway, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about MCP Zero-Trust Gateway: Provenance, Security disclosure, Schema quality, Stability and 2 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.