x402 Payment Request Parser
REMOTE · X402-SAFETY-KIT-PRODUCTION.MK-CAREER-PLANNING.WORKERS.DEV
x402 payment-request parser with a limited token list. Does not sign, approve or judge payments.
Available components
Last scanned (8 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 391 tokens (~97/item across 4 items; 4 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 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
- 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 4 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.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 67
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 · Probed https://x402-safety-kit-production.mk-career-planning.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mk-career-planning.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 62a608d12f78fd3a8d88d692f2a2cd87fd3 |
| SANs: *.mk-career-planning.workers.dev, mk-career-planning.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-safety-kit-production.mk-career-planning.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402-safety-kit-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://x402-safety-kit-production.mk-career-planning.workers.dev/mcp | Inconclusive | 406 |
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 →
catalog Catalog: tools, prices and limits ~27
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_limits | object | yes | Daily limits of paid calls (calls, usd, timezone) or a misconfiguration notice. |
| fetch_status_values | object | – | – |
| legal | object | yes | – |
| paused | object | yes | Operator pause flags (true = paused). |
| payment | object | yes | – |
| provenance | array | – | Freshness receipts for every upstream source used. |
| server | object | yes | – |
| terms | string | yes | URL of the terms of service. |
| tools | array | yes | Every tool of this server with its price. |
No examples provided.
get_receipt Get receipt of a paid call ~83
Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id returned with a paid result ("rcpt_" + 64 hex characters). |
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| receipt_id | string | yes | Receipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt. |
| result | – | yes | The stored result, exactly as returned by the paid call. |
| settled_at | string|null | yes | – |
| terms | string | yes | URL of the terms of service. |
| tool | string | yes | Name of the paid tool that produced the result. |
No examples provided.
x402_known_assets x402 known assets and networks table ~74
Free. The limited reference list this server compares token addresses with: known assets (network, contract, symbol, decimals) with sources and check dates, known CAIP-2 networks, scheme names from the x402 specs, and payment flows. A table match is not proof that an asset or a merchant is genuine.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | Known assets per CAIP-2 network. |
| networks | object | yes | – |
| payment_flows | object | yes | – |
| provenance | object | yes | Version and sources of the bundled asset table. |
| registry_version | string | yes | – |
| schemes | array | yes | – |
| terms | string | yes | URL of the terms of service. |
No examples provided.
x402_parse_payment_request Parse an x402 payment request ~207
Free. Decode one x402 v2 payment request (base64 PAYMENT-REQUIRED header, PaymentRequired JSON or MCP tool result) and list every accepts option with exact atomic and decimal amounts. Token addresses are compared with a limited reference list. status: parsed, ambiguous (options differ in recipient, network or amount; none is chosen), malformed or unsupported. Does not verify the merchant, authorize a transfer, assess fraud risk, or guarantee any payment. URLs in the input are never fetched.
| Name | Type | Req | Description |
|---|---|---|---|
| raw | – | yes | The payment request. A string: the base64 PAYMENT-REQUIRED header value (a leading 'PAYMENT-REQUIRED:' is allowed) or JSON text. An object: the PaymentRequired JSON, or for transport mcp the tool res… |
| transport | string | – | Where the request came from: http (402 response) or mcp (paid tool result). Default http. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_scope | object | yes | – |
| comparisons | array | yes | – |
| decoded_from | string|null | yes | – |
| errors | array | yes | – |
| evidence | array | yes | – |
| mismatches | array | yes | – |
| mode | string | yes | – |
| note | string | yes | – |
| parsed | – | yes | The decoded request with every accepts option (null unless status is parsed or ambiguous). |
| payment_required_location | – | yes | – |
| provenance | object | yes | Version and sources of the bundled asset table. |
| status | string | yes | parsed = the checked x402 v2 structure had no defects (not a statement about the merchant or whether to pay). ambiguous = options differ in recipient, network or amount; none was chosen. malformed /… |
| terms | string | yes | URL of the terms of service. |
| unsupported | array | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the x402 Payment Request Parser MCP server?
x402 Payment Request Parser is a hosted endpoint at https://x402-safety-kit-production.mk-career-planning.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · x402-safety-kit-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-x402-safety-kit 'https://x402-safety-kit-production.mk-career-planning.workers.dev/mcp'
What is the x402 Payment Request Parser MCP server?
x402 Payment Request Parser is an MCP server listed in the public MCP registry as io.github.mk-career-planning/x402-safety-kit. x402 payment-request parser with a limited token list. Does not sign, approve or judge payments. This page covers its hosted endpoint (https://x402-safety-kit-production.mk-career-planning.workers.dev/mcp).
Is the x402 Payment Request Parser MCP server safe to use?
x402 Payment Request Parser scores 67 out of 100 on VerifyMCP. 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 x402 Payment Request Parser MCP server expose?
x402 Payment Request Parser exposes 4 tools: catalog, x402_parse_payment_request, x402_known_assets, get_receipt. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Does the x402 Payment Request Parser MCP server require authentication?
No. We connected to x402 Payment Request Parser without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the x402 Payment Request Parser MCP server still maintained?
x402 Payment Request Parser 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.