Skip to main content
Glama
x402 Oracle MCP (Base USDC)

x402 Oracle MCP (Base USDC)

oracle_review_mcp

Audit paid MCP server architecture for x402 payment wrapping, discovery metadata, health tools, Streamable HTTP compliance, and seller-key isolation before deployment.

Instructions

Audit a paid MCP server architecture for x402 payment wrapping, declareDiscoveryExtension metadata, free health tooling, Streamable HTTP compliance, and seller-key isolation ($3.00 USDC on Base). Unpaid calls return 402 terms. Use oracle_bazaar_rewrite for listing copy or oracle_diagnose_402 for single header checks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mcp_url": "<mcp_url>"
    },
    "name": "oracle_review_mcp"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional transport, runtime, and paid tool summary (e.g. 'streamable-http, two paid tools').
mcp_urlYesPublic MCP endpoint URL or deployment path under review (e.g. 'https://example.com/mcp').

Output Schema

NameRequiredDescriptionDefault
riskNoDeployment and key-exposure hazards detected.
wisdomYesBest-practice design checklist for Bazaar-ready paid MCP servers.
verdictYesArchitectural review verdict summarizing required gaps.
citationsNox402 MCP server reference links.
implementation_promptNoTargeted code refactor plan for the audited MCP server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / mcp_url / description
      Added value: +"Public MCP endpoint URL or deployment path under review (e.g. 'https://example.com/mcp')."
    • addedInput schema / properties / mcp_url / minLength
      Added value: +1
    • addedInput schema / properties / notes / description
      Added value: +"Optional transport, runtime, and paid tool summary (e.g. 'streamable-http, two paid tools')."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "citations": {
      +      "description": "x402 MCP server reference links.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "implementation_prompt": {
      +      "description": "Targeted code refactor plan for the audited MCP server.",
      +      "type": "string"
      +    },
      +    "risk": {
      +      "description": "Deployment and key-exposure hazards detected.",
      +      "type": "string"
      +    },
      +    "verdict": {
      +      "description": "Architectural review verdict summarizing required gaps.",
      +      "type": "string"
      +    },
      +    "wisdom": {
      +      "description": "Best-practice design checklist for Bazaar-ready paid MCP servers.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "verdict",
      +    "wisdom"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior. The description adds important commercial behavior: the $3.00 USDC on Base price and 402 terms for unpaid calls. It does not explain how payment is satisfied or why the operation is non-read-only, so a minor gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and audit checklist, then adds payment behavior and sibling routing in two short sentences. The description is dense but has no wasted filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter audit tool with annotations and an output schema, the description covers purpose, audit scope, cost/payment behavior, and key alternatives. Response-format details can be supplied by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for both mcp_url and notes, including examples and constraints. The description adds no extra meaning, syntax, or usage detail for the parameters, so the high-coverage baseline applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Audit') and resource ('paid MCP server architecture'), then enumerates the exact audit targets. The final sentence names sibling alternatives, so the tool is distinguishable without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for full architecture reviews and explicitly routes listing copy to oracle_bazaar_rewrite and single-header checks to oracle_diagnose_402. Although it does not list every sibling, the named alternatives cover the adjacent use cases most likely to cause misselection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.