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.

PrufGate

PYPI · PRUFGATE

Read-only tools that check whether code, and the tests that claim it works, are real.

Available components

+15 this week 79 Trust /100

Last scanned (11 minutes ago)

Scores higher than 78% of PyPI servers

Category Testing and QA

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
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to GuardianVigil-Labs/Prufgate). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 675 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: 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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 64

    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 5 Nov 2026 · Analysed pypi/prufgate@1.1.0

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo GuardianVigil-Labs/Prufgate
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/GuardianVigil-Labs/Prufgate/.github/workflows/release.yml@refs/tags/v1.1.0
Rekor log index 3480554494
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:85d05566702f8a60768af50b99488b8d0a938b8ba5604045199c0c82740a8216

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

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

Dependencies 1 package
Packages resolved 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~675 tokens

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 →

Tool Tokens
prufgate_anti_fabrication ~80

Engine 1: canned fallbacks, simulated return values, stub handlers and other fabricated production logic.

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
changed_onlyboolean–Scan only changed files
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_bola_check ~82

Engine 5: routes and queries without auth or tenant scoping; the live two-token probe runs only when target_url is set.

NameTypeReqDescription
target_urlstring–Live http(s) URL for the two-token BOLA probe. The probe runs only when this is set.
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_contract_check ~78

Engine 4: undeclared or hallucinated imports, undocumented environment variables and frontend/backend route mismatches.

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
changed_onlyboolean–Scan only changed files
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_diff_guard ~68

Engine 3: skipped tests, suppression comments, unsafe casts and weakened lint/CI config added in the diff.

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_fast_scan ~74

Run engines 1-5 (anti-fabrication, test integrity, diff guard, contract guard, static BOLA) on changed files.

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_full_scan ~102

Run engines 1-5 on the whole workspace plus the diff reviewer; adds the live BOLA probe only when target_url is set.

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
target_urlstring–Live http(s) URL for the two-token BOLA probe. The probe runs only when this is set.
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_review ~68

Engine 6: deterministic review of the diff against base_ref (default: resolved like prufgate check --changed).

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_summary ~44

Read the last SARIF/Markdown report written by ./prufgate.sh without running a scan.

NameTypeReqDescription
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

prufgate_test_audit ~79

Engine 2: zero-assertion tests, tautologies, self-mocked units and weakened assertions.

NameTypeReqDescription
base_refstring–Base git ref to diff against, e.g. origin/main
changed_onlyboolean–Scan only changed files
workspace_pathstring–Path to the repository to scan

No output schema declared.

No examples provided.

Install

How do I install the PrufGate MCP server?

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

pypi · prufgate

# add to Claude Code
claude mcp add guardianvigil-labs-prufgate -- uvx prufgate
Common questions

What is the PrufGate MCP server?

PrufGate is an MCP server listed in the public MCP registry as io.github.GuardianVigil-Labs/prufgate. Read-only tools that check whether code, and the tests that claim it works, are real. This page covers its PyPI package (prufgate).

Is the PrufGate MCP server safe to use?

PrufGate scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.

What tools does the PrufGate MCP server expose?

PrufGate exposes 9 tools: prufgate_fast_scan, prufgate_full_scan, prufgate_anti_fabrication, prufgate_test_audit, prufgate_diff_guard, and 4 more. Their descriptions and schemas cost roughly 675 tokens of context every time the server is loaded.

Is the PrufGate MCP server still maintained?

PrufGate 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 PrufGate MCP server under?

PrufGate declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.