402shield
Server Details
x402 payment security and pre-execution transaction risk screening for autonomous AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly stated as preparing a paid 402Shield pre-execution safety check.
With a single tool named preflight_payment, there is no mixed naming convention to create inconsistency. The snake_case name is readable and unambiguous in context.
A single tool is thin for an MCP server surface, even though it matches a narrow paid-check adapter purpose. It falls below the typical well-scoped 3-15 tool range.
The tool only prepares the paid check and returns an endpoint; the MCP surface does not include tools to execute payment, retrieve the verdict, or check status directly. This is a notable lifecycle gap for agents needing end-to-end coverage.
Available Tools
1 toolpreflight_payment402Shield Preflight PaymentInspect
Prepare the exact paid 402Shield request that must be completed before an autonomous payment executes. Submit the returned POST request with an x402-capable client. The paid response is ALLOW, REVIEW, or BLOCK. Execute the intended payment only after ALLOW; REVIEW and BLOCK should stop execution by default. Price: $0.005 USDC.
| Name | Required | Description | Default |
|---|---|---|---|
| policy | No | ||
| expected | No | ||
| requestId | No | ||
| requested | Yes | ||
| transaction | No | ||
| transactionPolicy | No | ||
| expectedTransaction | No | ||
| simulateTransaction | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| body | Yes | |
| price | Yes | |
| action | Yes | |
| method | Yes | |
| network | Yes | |
| service | Yes | |
| advisory | Yes | |
| contentType | Yes | |
| executionRule | Yes | |
| paymentRequired | Yes | |
| expectedDecisionValues | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
preflight_payment1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "action": { + "const": "execute_x402_request", + "type": "string" + }, + "advisory": { + "const": true, + "type": "boolean" + }, + "body": { + "additionalProperties": {}, + "propertyNames": { + "type": "string" + }, + "type": "object" + }, + "contentType": { + "const": "application/json", + "type": "string" + }, + "executionRule": { + "type": "string" + }, + "expectedDecisionValues": { + "items": { + "enum": [ + "ALLOW", + "REVIEW", + "BLOCK" + ], + "type": "string" + }, + "type": "array" + }, + "method": { + "const": "POST", + "type": "string" + }, + "network": { + "type": "string" + }, + "paymentRequired": { + "const": true, + "type": "boolean" + }, + "price": { + "const": "$0.005", + "type": "string" + }, + "service": { + "const": "402Shield", + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "service", + "action", + "method", + "url", + "price", + "network", + "contentType", + "body", + "paymentRequired", + "expectedDecisionValues", + "executionRule", + "advisory" + ], + "type": "object" +}
1 tool update
- First observed
preflight_payment
Related MCP Connectors
AI agent execution safety via x402 micropayments: risk scoring, integrity, memory checks
Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.
Counterparty risk scoring for agentic commerce via x402 micropayments.
Paid token risk and security intelligence for AI agents over MCP with x402 payments.
Related MCP Servers
- AlicenseAqualityAmaintenancex402-trust gives AI agents a "check before you pay" layer for the x402 ecosystem.15295 npmMIT

AgentRiskofficial
FlicenseNot gradedqualityBmaintenancePre-Trade Security & Risk Analysis Layer for Autonomous DeFi Agents on Base using x402 protocol.-- AlicenseAqualityBmaintenanceBefore an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.3MIT
- AlicenseNot gradedqualityCmaintenanceCrypto compliance tools for AI-agent payments: screen any address for sanctions, frozen-stablecoin and hacker/mixer exposure across 8+ chains, trace fund taint, and get an allow/review/decline decision before settlement. Free keyless address checks; deeper endpoints are x402-payable.314 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.