io.github.arden-instance/x402lint
PYPI · X402LINT
Lint an HTTP endpoint's x402 402 conformance; decode X-PAYMENT blobs; inspect a facilitator.
Available components
Last scanned (11 hours ago)
Scores higher than 58% of PyPI servers
Category Security
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. 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 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 265 tokens (~88/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
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 →
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.
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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/x402lint@0.5.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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_facilitator ~60
Fetch a facilitator's /supported endpoint and summarise which scheme/network/version combinations it settles, plus any interop warnings. Pass the facilitator base URL (defaults to x402.org).
| Name | Type | Req | Description |
|---|---|---|---|
| timeout | number | – | – |
| url | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
decode_payment ~60
Decode a base64 (std or url-safe) JSON blob - an X-PAYMENT header, a PaymentRequirements 'accepts' entry, or a settlement response - and classify what kind of x402 document it is.
| Name | Type | Req | Description |
|---|---|---|---|
| blob | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_endpoint ~86
Fetch an HTTP endpoint unpaid, expect an x402 402 challenge, and lint it against the spec. Returns {url, wire_version, ok, counts, checks[]} where each check has id/level (PASS|WARN|FAIL|INFO)/message.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| method | string | – | – |
| timeout | number | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.arden-instance/x402lint MCP server?
io.github.arden-instance/x402lint runs locally as a PyPI package, launched with uvx --from 'x402lint[mcp]' x402lint mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · x402lint
claude mcp add arden-instance-x402lint -- uvx --from 'x402lint[mcp]' x402lint mcp
What is the io.github.arden-instance/x402lint MCP server?
io.github.arden-instance/x402lint is an MCP server listed in the public MCP registry as io.github.arden-instance/x402lint. Lint an HTTP endpoint's x402 402 conformance; decode X-PAYMENT blobs; inspect a facilitator. This page covers its PyPI package (x402lint).
Is the io.github.arden-instance/x402lint MCP server safe to use?
io.github.arden-instance/x402lint scores 66 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 io.github.arden-instance/x402lint MCP server expose?
io.github.arden-instance/x402lint exposes 3 tools: lint_endpoint, decode_payment, check_facilitator. Their descriptions and schemas cost roughly 206 tokens of context every time the server is loaded.
Is the io.github.arden-instance/x402lint MCP server still maintained?
io.github.arden-instance/x402lint 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 io.github.arden-instance/x402lint MCP server under?
io.github.arden-instance/x402lint 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 io.github.arden-instance/x402lint MCP server?
VerifyMCP ran 15 checks on io.github.arden-instance/x402lint, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.arden-instance/x402lint: Malware scan. 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.