JSON Recon MCP Server

MCP tools for concise Schema.org extraction and field-level Product verification.

Tools and prices

| Tool | Mode | Price on success | | --- | --- | ---: | | check_extractability | Free preflight | $0 | | extract_schema | Lite | $0.005 | | extract_schema | Full | $0.01 | | verify_product | Verified Product | $0.02 |

Paid tools support either a prepaid JSON Recon API key or an agent-controlled wallet using x402 on Base. The free preflight works without credentials.

The examples pin the reviewed release. Its published shrinkwrap also locks transitive dependencies; update the version deliberately when adopting a newer release.

Prepaid API-key setup

{
  "mcpServers": {
    "jsonrecon": {
      "command": "npx",
      "args": ["-y", "@jsonrecon/[email protected]"],
      "env": {
        "JSONRECON_API_KEY": "jr_liv_xxxxx"
      }
    }
  }
}

x402 wallet setup

{
  "mcpServers": {
    "jsonrecon": {
      "command": "npx",
      "args": ["-y", "@jsonrecon/[email protected]"],
      "env": {
        "JSONRECON_PAYMENT_MODE": "x402",
        "JSONRECON_EVM_PRIVATE_KEY": "0x_your_32_byte_private_key",
        "JSONRECON_X402_SESSION_LIMIT_USDC": "1.00"
      }
    }
  }
}

Use a dedicated, low-balance agent wallet. The private key remains in the local MCP process and is never sent to JSON Recon; only the signed x402 payment authorization is transmitted. The client signs only exact Base-mainnet USDC challenges from the configured JSON Recon origin and route, subject to fixed per-route price ceilings. Redirects are disabled. The default cumulative authorization ceiling is $1 USDC per MCP process and can be lowered with JSONRECON_X402_SESSION_LIMIT_USDC.

When both credentials are configured, the default auto mode prefers the API key. Set JSONRECON_PAYMENT_MODE explicitly to api_key or x402 to override that selection.

Product price types

Parseable Product offer prices are JSON numbers, such as 17.99, rather than numeric strings. Retained source text can remain a string, so accept number | string for prices. In Verified Product, verification.fields.price.value follows the assessed Product price. Individual verification.fields.price.sources[].value entries preserve their source representation and can mix strings and numbers, including within the same response. Missing prices are optional; offers can be one object or an array.

Free-only setup

Omit the env block to use check_extractability without credentials. Paid tool calls return a configuration error until either payment method is configured.

Learn more at jsonrecon.com/mcp.