Loading ToolBench
Express middleware wrapper for x402 payment protocol integration with Base network USDC payments
This is not an MCP server, it is an Express.js middleware library for x402 payment processing. The single tool 'requirePayment' lacks proper MCP registration, has a vague description in Spanish, and exposes cryptographic parameters as tool inputs. The schema is partially visible but incomplete. No tool definitions, no MCP protocol implementation, no resource/prompt/logging support. This appears to be a payment SDK, not an MCP tool server.
Middleware Express para proteger un endpoint con precio x402.
Not an MCP server. This is an Express.js middleware library, not a Model Context Protocol server. No MCP transport, no tool registration via MCP, no protocol handshake.
Tool name 'requirePayment' does not follow verb_noun convention. Should be 'process_payment' or 'settle_payment' to clearly signal the action.
Description is in Spanish ('Middleware Express para proteger un endpoint con precio x402') and lacks clarity on what the tool does, when to use it, and what it returns. Under 20 chars of useful English context.
Cryptographic secrets exposed as tool parameters: 'payment-signature' header contains Base64-encoded JSON with nonce and signature. These should never be tool parameters, use server-side secret injection.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 16 | 2026-07-28+ | v2 |
Input schema incomplete. 'amountRaw' is a string with minimal description. 'payment-signature' is marked as a header location but lacks type, format, and validation constraints. No output schema documented.