io.github.dario933/x402-paid-checks
NPM · X402-PAID-CHECKS-MCP
Domain, email, vendor and ransomware checks paid per call in USDC via x402 from your wallet.
Available components
Last scanned (7 hours ago)
Scores higher than 32% of npm 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 Security99
- 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
- 30 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. 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 11 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7733 tokens (~145/item across 53 items; 53 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 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 53 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 53 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
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.
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.
- 30 Oct 26 +3
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 46
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 5 Nov 2026 · Analysed npm/x402-paid-checks-mcp@0.1.1
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 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 30 |
| 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 →
vendorsafety_vendor_safety Vendor Safety Check: GET /v1/vendor-safety ~144
Should we trust this vendor? One-call vendor safety check for a domain. $0.04 USDC on Base per call. Combines TLS certificate, DNS/DMARC, email-security score, ransomware leak-site claims (claims, not confirmed) and live outage status into a safe/caution/risk/incomplete verdict with reasons. Charged only if at least one check returns real data. Don't use this as proof of a breach. [x402: pays from the caller's wallet (X402_PRIVATE_KEY); without a key the tool returns the live 402 price only.]
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | domain |
| vendor | string | – | vendor |
No output schema declared.
No examples provided.
watchlist_watchlists Dragons Eye Watchlist: POST /v1/watchlists ~143
Create a Dragons Eye watchlist from a list of entries (such as vendor domains), with a delivery target like a webhook_url, for ransomware claim alerts. POST /v1/watchlists. $2.00 USDC on Base per call. Covers up to 25 domains for 30 days; the response shows manage_token and webhook_secret once. For a one-time check, use the Dragons Eye lookup or bulk-check tools. [x402: pays from the caller's wallet (X402_PRIVATE_KEY); without a key the tool returns the live 402 price only.]
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | – | yes | JSON body field delivery |
| entries | – | yes | JSON body field entries |
No output schema declared.
No examples provided.
watchlist_watchlists_renew Dragons Eye Watchlist: POST /v1/watchlists/renew ~132
Renew an existing Dragons Eye watchlist by watchlist_id. You need the Authorization: Bearer manage_token you got when it was created. POST /v1/watchlists/renew. $2.00 USDC on Base per call. Adds 30 days. Don't use this to create a new watchlist; use /v1/watchlists. [x402: pays from the caller's wallet (X402_PRIVATE_KEY); without a key the tool returns the live 402 price only.]
| Name | Type | Req | Description |
|---|---|---|---|
| Authorization | string | yes | Authorization |
| watchlist_id | – | yes | JSON body field watchlist_id |
No output schema declared.
No examples provided.
How do I install the io.github.dario933/x402-paid-checks MCP server?
io.github.dario933/x402-paid-checks runs locally as an npm package, launched with npx -y x402-paid-checks-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 · x402-paid-checks-mcp
claude mcp add dario933-x402-paid-checks -- npx -y x402-paid-checks-mcp
What is the io.github.dario933/x402-paid-checks MCP server?
io.github.dario933/x402-paid-checks is an MCP server listed in the public MCP registry as io.github.dario933/x402-paid-checks. Domain, email, vendor and ransomware checks paid per call in USDC via x402 from your wallet. This page covers its npm package (x402-paid-checks-mcp).
Is the io.github.dario933/x402-paid-checks MCP server safe to use?
io.github.dario933/x402-paid-checks scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.dario933/x402-paid-checks MCP server expose?
io.github.dario933/x402-paid-checks exposes 53 tools: orioncmd_cert, orioncmd_dns, orioncmd_expiry, orioncmd_email_auth, orioncmd_headers, and 48 more. Their descriptions and schemas cost roughly 7,733 tokens of context every time the server is loaded.
Is the io.github.dario933/x402-paid-checks MCP server still maintained?
io.github.dario933/x402-paid-checks 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 io.github.dario933/x402-paid-checks MCP server under?
io.github.dario933/x402-paid-checks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.