# x402Shield (remote · x402shield.dev)

Public demo: evaluate AI-agent payment authorization and approval policy. No signing, no settlement.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `x402shield.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-x402shield-x402shield/api-mcp.md), [page](https://verifymcp.io/servers/dev-x402shield-x402shield/api-mcp)

## Channel facts

- Endpoint: `https://x402shield.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 449 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-x402shield-x402shield 'https://x402shield.dev/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-x402shield-x402shield": {
      "url": "https://x402shield.dev/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-x402shield-x402shield": {
      "type": "http",
      "url": "https://x402shield.dev/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-x402shield-x402shield]
url = "https://x402shield.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-x402shield-x402shield": {
      "type": "remote",
      "url": "https://x402shield.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-x402shield-x402shield --url 'https://x402shield.dev/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-x402shield-x402shield:
    url: "https://x402shield.dev/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-x402shield-x402shield": {
      "Transport": "http",
      "Url": "https://x402shield.dev/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-x402shield-x402shield -t streamable-http -u 'https://x402shield.dev/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-x402shield-x402shield": {
      "type": "http",
      "url": "https://x402shield.dev/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 69, +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.

### 2026-10-14 (score 68, +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.

### 2026-10-12 (score 67, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 66)

First indexed and scored.

## MCP tools (5)

### `x402shield_get_demo_policy` (~69 tokens)

Get demo authorization policy

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.

### `x402shield_authorize_payment` (~178 tokens)

Check whether a proposed payment is authorized

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.

Input parameters:

- `amountUsdc` (number, required): Proposed payment amount in USDC (0.01-5000).
- `presetId` (string, required): 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.

### `x402shield_get_authorization` (~59 tokens)

Get a previously-decided authorization by id

Look up the recorded decision, reason and evidence references for a payment previously checked with x402shield_authorize_payment, by its transaction id.

Input parameters:

- `txId` (string, required): The txId returned by x402shield_authorize_payment.

### `x402shield_list_demo_transactions` (~70 tokens)

List recent demo authorization decisions

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.

Input parameters:

- `limit` (integer): Maximum rows to return (default 10, max 20).

### `x402shield_get_evidence` (~73 tokens)

Get the authorization evidence for a decision

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.

Input parameters:

- `txId` (string, required): The txId returned by x402shield_authorize_payment.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-x402shield-x402shield/api-mcp#diagnostics

## Score history

- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 67
- 2026-10-12: 67
- 2026-10-10: 66

## Common questions

### 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 70 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 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://x402shield.dev/api/mcp
- Website: https://x402shield.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-x402shield-x402shield/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-x402shield-x402shield/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-x402shield-x402shield/api-mcp