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.

Preflight Checks (x402)

NPM · @JOSEROBLES/PREFLIGHT-MCP

Deterministic pre-execution verification tools for AI agents with x402 USDC pay-per-call on Base

56 Trust /100

Last scanned (8 hours ago)

Scores higher than 36% of npm 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 18 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 849 tokens (~106/item across 8 items; 8 tools + 0 resources), lean.Pass
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
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.

  • 16 Oct 26 56

    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 17 Oct 2026 · Analysed npm/@joserobles/preflight-mcp@0.4.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 115 packages
Packages resolved 115
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~849 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
preflight_ai_act_obligations ~126

Call when you need to know which articles of the EU AI Act mention a given obligation for a given role. Returns the matching articles with headings, excerpts and EUR-Lex links from a pinned corpus version. Retrieval over the official text: it does not classify your system or assess compliance. Paid: $0.10 via x402.

NameTypeReqDescription
autonomy_levelstring––
domainstring––
risk_tierstring––
rolestring––
system_typestring––
topicstring––

No output schema declared.

No examples provided.

preflight_btc_tx_context ~90

Call before signing a Bitcoin transaction when you need chain context for its inputs. Returns for each prevout whether it exists, whether it is already spent, its value in sats and its confirmations, with source links. Describes on-chain facts; never advises whether to sign. Paid: $0.10 via x402.

NameTypeReqDescription
inputsarrayyes–
networkstring––

No output schema declared.

No examples provided.

preflight_check_cve ~109

Call before acting on CVE identifiers produced by a model. Returns whether each CVE record exists and its state (published or rejected), with severity and the official CVE record link. Catches fabricated advisory references; does not tell you whether to patch. Paid: $0.05 via x402.

NameTypeReqDescription
cve_idstring––
idsarray––
productstring––
vendorstring––
versionstring––

No output schema declared.

No examples provided.

preflight_check_deps ~87

Call before installing packages suggested by a language model. Returns whether each npm/PyPI/crates package exists, whether it is deprecated or yanked, and the closest real names when it is not found. Never inspects contents and never returns a safety verdict. Paid: $0.05 via x402.

NameTypeReqDescription
ecosystemstringyes–
packagesarrayyes–

No output schema declared.

No examples provided.

preflight_check_deps_version ~117

Call before pinning or installing a specific package version in npm, PyPI or crates.io. Returns whether that exact version exists in the official registry, its publication timestamp, whether it is deprecated or yanked, its published artifact hashes, and whether an expected SRI/hex digest matches. Paid: $0.05 via x402.

NameTypeReqDescription
ecosystemstringyes–
expected_integritystring––
filenamestring––
namestringyes–
versionstringyes–

No output schema declared.

No examples provided.

preflight_check_legal_citation ~104

Call before publishing a claim that cites EU law. Checks that the cited instrument exists in the pinned corpus, that the cited article exists within it, and whether your quoted text appears in that article, returning the official text with a EUR-Lex link. Citation verification only: it never gives legal advice. Paid: $0.10 via x402.

NameTypeReqDescription
articlestringyes–
instrumentstringyes–
quotestring––

No output schema declared.

No examples provided.

preflight_inspect_btc ~98

Call before signing or broadcasting a Bitcoin transaction. Decodes a raw transaction hex or a PSBT and returns inputs, outputs, script types, addresses and objective signals (RBF, dust, unsigned inputs). Parses only the bytes you send; never advises whether to sign. Paid: $0.10 via x402.

NameTypeReqDescription
networkstring––
psbtstring––
rawstring––

No output schema declared.

No examples provided.

preflight_inspect_evm ~118

Call before signing an Ethereum or Base transaction or calldata. Decodes raw transaction bytes or contract calldata against standard interfaces (ERC-20, ERC-721, ERC-1155, WETH, EIP-2612 Permit and Permit2) in memory. Mechanical byte decoding only: never simulates state or advises whether to sign. Paid: $0.10 via x402.

NameTypeReqDescription
calldatastring––
networkstringyes–
raw_txstring––
tostring––

No output schema declared.

No examples provided.

Install

How do I install the Preflight Checks (x402) MCP server?

Preflight Checks (x402) runs locally as an npm package, launched with npx -y @joserobles/preflight-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @joserobles/preflight-mcp

# add to Claude Code
claude mcp add josediegorobles-preflight-checks -- npx -y @joserobles/preflight-mcp
Common questions

What is the Preflight Checks (x402) MCP server?

Preflight Checks (x402) is an MCP server listed in the public MCP registry as io.github.josediegorobles/preflight-checks. Deterministic pre-execution verification tools for AI agents with x402 USDC pay-per-call on Base. This page covers its npm package (@joserobles/preflight-mcp).

Is the Preflight Checks (x402) MCP server safe to use?

Preflight Checks (x402) scores 56 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 17 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 Preflight Checks (x402) MCP server expose?

Preflight Checks (x402) exposes 8 tools: preflight_check_deps, preflight_inspect_btc, preflight_btc_tx_context, preflight_check_legal_citation, preflight_check_cve, and 3 more. Their descriptions and schemas cost roughly 849 tokens of context every time the server is loaded.

Is the Preflight Checks (x402) MCP server still maintained?

Preflight Checks (x402) is still listed as active in the MCP registry. We last reached this channel on 17 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 Preflight Checks (x402) MCP server under?

Preflight Checks (x402) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.