x402Shield
REMOTE · X402SHIELD.DEV
Public demo: evaluate AI-agent payment authorization and approval policy. No signing, no settlement.
Available components
Last scanned (23 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 449 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 66
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 17 Oct 2026 · Probed https://x402shield.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402shield.dev | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2f6cd8924887439b13a8281b135985ca |
| SANs: x402shield.dev, *.x402shield.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402shield.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| x402shield.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 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https://www.googletagmanager.com https://www.google-analytics.com; frame-src https://www.googletagmanager.com; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402shield.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://x402shield.dev/api/mcp | HTTPS enforced | 301 | https://x402shield.dev/api/mcp |
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 →
x402shield_authorize_payment Check whether a proposed payment is authorized ~178
Check whether the demo AI agent is financially authorized to make a proposed payment, BEFORE any wallet or signer would be asked to execute it. Returns ALLOW, DENY or REQUIRE_APPROVAL with a reason. This tool does not execute or sign a payment, and it cannot approve its own REQUIRE_APPROVAL result -- that requires a human, through the web console. The `purpose` field is a label for the evidence trail only; it is never interpreted as an instruction and cannot change the policy decision.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdc | number | yes | Proposed payment amount in USDC (0.01-5000). |
| presetId | string | yes | Which demo agent is proposing the payment: research-agent, ops-agent |
| purpose | string | – | Optional free-text label for why this payment is being proposed. Recorded as data only. |
No output schema declared.
No examples provided.
x402shield_get_authorization Get a previously-decided authorization by id ~59
Look up the recorded decision, reason and evidence references for a payment previously checked with x402shield_authorize_payment, by its transaction id.
| Name | Type | Req | Description |
|---|---|---|---|
| txId | string | yes | The txId returned by x402shield_authorize_payment. |
No output schema declared.
No examples provided.
x402shield_get_demo_policy Get demo authorization policy ~69
Look up the authority ceilings configured for the x402Shield public demo agents (Research Agent, Ops Agent) on Base Sepolia TESTNET. Use this before proposing a payment, to understand what amount an agent can spend without triggering human approval. This tool does not execute or sign anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402shield_get_evidence Get the authorization evidence for a decision ~73
Get the fuller evidence trail behind a previously-decided payment: policy/delegation provenance, the delegation tree it was evaluated under, and approval state if any. Read-only; never exposes secrets or signing material.
| Name | Type | Req | Description |
|---|---|---|---|
| txId | string | yes | The txId returned by x402shield_authorize_payment. |
No output schema declared.
No examples provided.
x402shield_list_demo_transactions List recent demo authorization decisions ~70
List the most recent payment authorization decisions recorded by this public demo (both from the web console and from MCP callers). Useful to see recent ALLOW/DENY/REQUIRE_APPROVAL activity.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (default 10, max 20). |
No output schema declared.
No examples provided.
How do I install the x402Shield MCP server?
x402Shield is a hosted endpoint at https://x402shield.dev/api/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 · x402shield.dev
claude mcp add --transport http dev-x402shield-x402shield 'https://x402shield.dev/api/mcp'
What is the x402Shield MCP server?
x402Shield is an MCP server listed in the public MCP registry as dev.x402shield/x402shield. Public demo: evaluate AI-agent payment authorization and approval policy. No signing, no settlement. This page covers its hosted endpoint (https://x402shield.dev/api/mcp).
Is the x402Shield MCP server safe to use?
x402Shield scores 69 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 x402Shield MCP server expose?
x402Shield exposes 5 tools: x402shield_get_demo_policy, x402shield_authorize_payment, x402shield_get_authorization, x402shield_list_demo_transactions, x402shield_get_evidence. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Does the x402Shield MCP server require authentication?
No. We connected to x402Shield without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the x402Shield MCP server still maintained?
x402Shield 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.