vet402-check
NPM · @VET402/CHECK
Before your agent pays an x402 API, check if vet402 bought it with its own money and what came back.
Available components
Last scanned (13 hours ago)
Scores higher than 38% of npm servers
Category Finance and Payments
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
- No install/post-install scripts declared.Pass
- 0 of 68 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 901 tokens (~300/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 17 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- Known CVEs: partial → pass ▲ security
- First check of Judged manipulation: pass security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Dependency health: partial → 1.00 functional
- 16 Oct 26 −1
- Known CVEs: pass → partial ▼ security
- Dependency health: 1.00 → partial functional
- 14 Oct 26 0
- Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess. functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 39
First indexed and scored.
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 18 Oct 2026 · Analysed npm/@vet402/check@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 68 packages
| Packages resolved | 68 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_before_paying Look an x402 or MPP seller up in vet402's public record ~411
Give the URL you are about to pay (and, if you have them, the chain and the payTo from the 402). Returns what vet402's public record holds about that seller: how many purchases vet402 made with its own money on Solana, Tempo, Base or Algorand, how many settled, how many came back with an answer, the newest purchase with its tx, the failures counted against the seller and the ones that are not, the grade as vet402 prints it (measuring while there are too few purchases), the signed records published for that seller, and whether the payTo matches one vet402 recorded. If vet402 has no record of the seller, it says so. The answer starts with a verdict (pay, avoid or unknown) and one sentence of why, from the same numbers: pay when vet402's paid purchases came back with an answer often enough, avoid when they mostly did not (only failures on the seller's side count), unknown when there is too little to tell. Reads public files only: no key, no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | The amount in the 402, in atomic units; compared with what vet402 paid for this URL (reason price_jump) |
| asset | string | – | The asset in the 402 (mint or token address); compared with the assets vet402 paid this seller in (reason asset_unseen) |
| chain | string | – | solana, tempo, base, algorand, or a CAIP-2 id such as eip155:8453 |
| explain | boolean | – | Also list the purchases the answer rests on, with date and tx |
| pay_to | string | – | The payTo (recipient) in the 402 you hold |
| url | string | yes | The resource URL about to be paid |
| verify_newest_record | boolean | – | Also verify the newest signed record of this seller (signature, Merkle proof, payment and anchor on chain) |
No output schema declared.
No examples provided.
diagnose_failed_payment Diagnose an x402 payment that brought no answer ~256
Give the transaction of a payment you made (a Solana signature or a Base tx hash), the URL you paid and, if you have it, the HTTP status the seller answered. Reads the payment from public RPC (settled or not, payTo, amount, asset, time) and puts it next to vet402's own purchases from the same seller on the same chain within 24 hours. Returns fault: seller_side, facilitator_side, buyer_side or undetermined, with reasons. seller_side needs a settled payment to a payTo vet402 paid this seller, a status vet402's rules put on the seller, and vet402's own paid purchases in the window failing too with none delivered; anything less is undetermined. For seller_side it adds an evidence pack (JSON and Markdown) to hand to the seller; nothing is sent. Reads public data only: no key, no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | solana or base (default: from the shape of tx) |
| status | integer | – | The HTTP status the seller answered after the payment |
| tx | string | yes | Solana transaction signature or Base tx hash of the payment |
| url | string | yes | The URL that was paid |
No output schema declared.
No examples provided.
verify_record Verify one vet402 signed record ~179
Give a record id (obs_YYYY-MM-DD_NNNNNN) or the https URL of a published record. Checks, without taking vet402's word for it: the bytes are the ones the records index lists, the signer is a vet402 observation key, the EIP-712 signature, that the verdict follows from the recorded checks, the Merkle proof to the day's root, the payment on chain over public RPC, and the day's root in a Solana memo sent by vet402's anchor wallet. Result: OK, OK_NOT_ANCHORED, OK_OFFLINE or FAIL, with one line per check.
| Name | Type | Req | Description |
|---|---|---|---|
| offline | boolean | – | Skip the reads from chain (payment and anchor) |
| record | string | yes | Record id (obs_2026-09-28_000164) or https URL of a record JSON |
No output schema declared.
No examples provided.
How do I install the vet402-check MCP server?
vet402-check runs locally as an npm package, launched with npx -y @vet402/check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @vet402/check
claude mcp add kzmttkc-vet402-check -- npx -y @vet402/check
What is the vet402-check MCP server?
vet402-check is an MCP server listed in the public MCP registry as io.github.kzmttkc/vet402-check. Before your agent pays an x402 API, check if vet402 bought it with its own money and what came back. This page covers its npm package (@vet402/check).
Is the vet402-check MCP server safe to use?
vet402-check scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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 vet402-check MCP server expose?
vet402-check exposes 3 tools: check_before_paying, verify_record, diagnose_failed_payment. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the vet402-check MCP server still maintained?
vet402-check is still listed as active in the MCP registry. We last reached this channel on 18 October 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 vet402-check MCP server under?
vet402-check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.