vet402
vet402 — independent verification of the x402 agent-payment economy: it buys what endpoints actually sell, verifies fulfillment against the seller's own declaration, and publishes the results with evidence (formerly Vouch).
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
kzmttkc
Source: github_repo_search
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
GRAPH_API_KEYETHOnline 2026 window (2026-09-05) — the same gate as check_resource_decision, but it holds the signer. On anything other than ALLOW the payment module is never loaded, so no signature can exist. Refusals are machine-readable and happen before a signature. Delegates the payment itself to payOrRefuse in @vet402/sdk. Signing requires VOUCH_PAYER_PRIVATE_KEY and viem; without them the gate still runs and refuses with payer_not_configured. Settlement is reported as settle_claimed — never settled, which only an on-chain re-read may write. Since 2026-09-06 it also takes policy (requireVet402Allow, evidence.source / minSubgraphReceipts / minL1Deliveries), forwarded to payOrRefuse unchanged: source: "subgraph" reads The Graph's x402 Base subgraph (key from GRAPH_API_KEY) and returns that read on decision_record.evidence[]. A seller outside the catalogue (/decision 404) is judged too when resource is given: the SDK reads the 402's payTo, that address's payee score and the caller's floors (reason_codes carries resource_uncatalogued); without resource a 404 refuses with evidence_unavailableVOUCH_API_KEYOptional since 2026-09-07: check_resource_decision and pay_if_trusted read /decision key-less (10/min per IP, then 429 rate_limited). The score and attest tools still need one (the API answers missing_api_key). [Create one here](https://vet402.com/dashboard/keys).VOUCH_API_URLAPI base URL. Override only to point at another deployment.VOUCH_PAYER_PRIVATE_KEYETHOnline 2026 window (2026-09-05) — the same gate as check_resource_decision, but it holds the signer. On anything other than ALLOW the payment module is never loaded, so no signature can exist. Refusals are machine-readable and happen before a signature. Delegates the payment itself to payOrRefuse in @vet402/sdk. Signing requires VOUCH_PAYER_PRIVATE_KEY and viem; without them the gate still runs and refuses with payer_not_configured. Settlement is reported as settle_claimed — never settled, which only an on-chain re-read may write. Since 2026-09-06 it also takes policy (requireVet402Allow, evidence.source / minSubgraphReceipts / minL1Deliveries), forwarded to payOrRefuse unchanged: source: "subgraph" reads The Graph's x402 Base subgraph (key from GRAPH_API_KEY) and returns that read on decision_record.evidence[]. A seller outside the catalogue (/decision 404) is judged too when resource is given: the SDK reads the 402's payTo, that address's payee score and the caller's floors (reason_codes carries resource_uncatalogued); without resource a 404 refuses with evidence_unavailableVOUCH_TIMEOUT_MSPer-request timeout. Cannot be disabled — a lookup that never returns cannot be failed closed on. A malformed value falls back to the default rather than breaking every tool call.Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
7/7 tools missing one or more hints — check_agent_trust (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_wallet_trust (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_payee_trust (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
Only 3/7 tool handlers declare input schemas (43%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Secrets stay with their owner
1 secret sent to a request target we could not resolve (VOUCH_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party
Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.
Domain consistency
npm scope @vet402 doesn't match GitHub owner kzmttkc
Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/kzmttkc/vet402)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check