_ registry / mcp + a2a http-sse · checked 1h ago

mcp-x402

https://mcp-x402.onrender.com

Registry code: 6aca15fc3f738044

api record

SCRIPTMASTERLABS x402 Gateway: read-only discovery of x402 paid APIs and fresh payment requirements on Base. Caller controls authorization and spending.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp-x402.onrender.com/mcp
door code
58c20491368d63bf
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is mcp-x402 live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mcp-x402 free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-x402 have?
9 tools: omnigate_runtime_search, interfere, leviathan_interfere, spend_gate_check, omnigate_runtime_execute, omnigate_runtime_receipt, sml_discover, sml_status, ….
Is mcp-x402 safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 98.1%· all time 99%

latency
542ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1008 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
_ what it is for
used for
  • discover x402 paid apis
  • inspect x402 payment requirements
  • check gateway status
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
30

distinct

settlements
693

last 2026-10-30

received on chain
19.2678 USDC

concentrated, shared-payto

_ what it can do 9 tools
3 open 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • sml_discover reads open 24h ago

    Find the x402 Gateway contract and where to inspect fresh payment requirements. FREE.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • sml_status reads open 24h ago

    Check the public x402 Gateway identity and canonical payment rail. FREE.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • x402_contract reads open 24h ago

    Inspect the canonical x402 payment contract. Returns network, USDC asset, payTo, headers, and the rule for resolving fresh target requirements. FREE.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • omnigate_runtime_search unknown never probed

    OMNIGATE Runtime catalog search (FREE). Finds SML paid routes a runtime script can call with sml.call(id, {query|path|body}), with live per-call USDC prices, plus published capsules (ready-made scripts). Use this before omnigate_runtime_execute to pick route ids. Prices are the live upstream registry amounts; nothing here spends.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Max routes to return."
        },
        "query": {
          "type": "string",
          "default": "",
          "maxLength": 200,
          "description": "Keywords, e.g. \"short squeeze\", \"sec filings\", \"web extract\". Empty lists everything (capped)."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • interfere unknown never probed

    Coherent Gate (PAID, x402/USDC). Scores whether your trading-signal paths agree: confidence-weighted long/short/flat consensus, coherence 0-1, and a pass/block gate (pass needs a non-flat consensus and coherence at or above the threshold, default 0.6). Tiers by path count: scout ≤4 $0.01, standard ≤8 $0.05, beast ≤32 $0.25 (defaults). The $0.25 max tier is charged upfront; on the x402 rail the unused difference is recorded as owed (not yet auto-refunded); on the Arc escrow rail (arc_auth_id) only the used tier is captured. Optional ticker pulls extra paths from registered sources before charging. Max 32 paths. Not financial advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "paths": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "source",
              "direction",
              "confidence"
            ],
            "properties": {
              "source": {
                "type": "string",
                "maxLength": 64,
                "minLength": 1,
                "description": "Label for where this signal came from (1-64 chars)."
              },
              "direction": {
                "enum": [
                  "long",
                  "short",
                  "flat"
                ],
                "type": "string",
                "description": "Direction this path calls: long, short, or flat."
              },
              "confidence": {
                "type": "number",
                "maximum": 1,
                "minimum": 0,
                "description": "Weight 0-1 this path gets in the consensus."
              }
            },
            "additionalProperties": false
          },
          "default": [],
          "maxItems": 32,
          "description": "Coherent Gate: AI trading signal paths to check for coherence. Priced tiers: scout ≤4, standard ≤8, beast ≤32 (defaults); >32 hard-rejected."
        },
        "ticker": {
          "type": "string",
          "pattern": "^[A-Z]{1,10}$",
          "description": "Optional: pull extra paths for this ticker from registered path sources (see docs/COHERENT_GATE_PATH_SOURCES.md)."
        },
        "sources": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 64
          },
          "maxItems": 16,
          "description": "Optional path-source ids; default = all enabled verified sources. Requires ticker."
        },
        "arc_auth_id": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$",
          "description": "Arc rail: authId from AuthCaptureEscrow.authorize() for at least the max-tier amount to our receiver. Only the used tier is captured; the rest returns via reclaim() after expiry."
        },
        "payment_header": {
          "type": "string",
          "description": "Base64 X-PAYMENT EIP-3009 payload (standard rail)."
        },
        "wallet_address": {
          "type": "string",
          "description": "Agent wallet address (informational)."
        },
        "payment_tx_hash": {
          "type": "string",
          "description": "Base USDC tx hash (sovereign rail)."
        }
      },
      "additionalProperties": false
    }
    arguments 76 lines
  • leviathan_interfere unknown never probed

    Coherent Gate + Leviathan (PAID, x402/USDC). Fetches the SML Leviathan signal (squeeze, momentum, or all) for a ticker, adds it as one path with your optional paths and registered sources, then runs the same coherence check as interfere: consensus, coherence 0-1, pass/block gate. Same tiers and billing as interfere ($0.25 max tier charged upfront; x402 difference recorded as owed, Arc rail captures only the used tier). If Leviathan is unavailable it continues on the other paths; with no paths it errors before charging. Max 32 paths. Not financial advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ticker",
        "signal_type"
      ],
      "properties": {
        "paths": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "source",
              "direction",
              "confidence"
            ],
            "properties": {
              "source": {
                "type": "string",
                "maxLength": 64,
                "minLength": 1,
                "description": "Label for where this signal came from (1-64 chars)."
              },
              "direction": {
                "enum": [
                  "long",
                  "short",
                  "flat"
                ],
                "type": "string",
                "description": "Direction this path calls: long, short, or flat."
              },
              "confidence": {
                "type": "number",
                "maximum": 1,
                "minimum": 0,
                "description": "Weight 0-1 this path gets in the consensus."
              }
            },
            "additionalProperties": false
          },
          "default": [],
          "maxItems": 31,
          "description": "Coherent Gate: extra signal paths (Leviathan adds one; total ≤ 32)."
        },
        "ticker": {
          "type": "string",
          "pattern": "^[A-Z]{1,10}$",
          "description": "Ticker symbol, 1-10 uppercase letters (e.g. AAPL)."
        },
        "sources": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 64
          },
          "maxItems": 16,
          "description": "Optional path-source ids added alongside Leviathan; default = all enabled verified sources."
        },
        "arc_auth_id": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$",
          "description": "Arc rail: authId from AuthCaptureEscrow.authorize() for at least the max-tier amount to our receiver. Only the used tier is captured; the rest returns via reclaim() after expiry."
        },
        "signal_type": {
          "enum": [
            "squeeze",
            "momentum",
            "all"
          ],
          "type": "string",
          "description": "Which Leviathan signal to fetch and add as a path: squeeze, momentum, or all."
        },
        "payment_header": {
          "type": "string",
          "description": "Base64 X-PAYMENT EIP-3009 payload (standard rail)."
        },
        "wallet_address": {
          "type": "string",
          "description": "Agent wallet address (informational)."
        },
        "payment_tx_hash": {
          "type": "string",
          "description": "Base USDC tx hash (sovereign rail)."
        }
      },
      "additionalProperties": false
    }
    arguments 89 lines
  • spend_gate_check unknown 7d ago

    Spend Gate (PAID $0.005 USDC on Base via x402). Advisory payment assessment — no wallet signing or spending by the buyer: a real Provider Trust approval and price cap are mandatory; explicit package/history rejections block. Four distinct decision inputs vote pay-side/reject-side — provider_trust (Provider Trust verify_provider) and payload_safety (ScriptDocs vulnerability check, only when manifest_url names an npm/PyPI/crates package) — both vote with real verdicts via the fleet operator lane at $0 upstream toll, price_sanity (quote vs caller policy_cap_usdc or the v1 default cap table; cap-only in v1, no historical median), delivery_history (this host's OmniGate settlement/delivery ledger). Coherence = |Σ w·d| / Σ w with d=+1 pay-side, −1 reject-side, w=confidence; gate_pass requires a positive Provider Trust decision, a real within-cap quote, no explicit safety or delivery-history rejection, coherence ≥ 0.6, and a pay-side consensus. The verdict is advisory, not payment authorization. Paths with no data abstain (no_signal) and contribute nothing. Only on a gate pass does Jev review run (noul act probability + pay/reject/quarantine choice, model + token usage returned). Use for: vetting a payee/invoice immediately before an agent wallet pays it. Don't use when: you need an actual payment executed (this is a check, it moves no funds), a trading signal (use interfere), or a free lookup (there is none — unpaid calls return the payment challenge). Settlement to the canonical SML payTo on Base.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "payee",
        "quoted_amount"
      ],
      "properties": {
        "payee": {
          "type": "string",
          "maxLength": 2048,
          "minLength": 1,
          "description": "Payee domain (e.g. \"api.example.com\") and/or full endpoint URL the wallet is about to pay."
        },
        "manifest_url": {
          "type": "string",
          "format": "uri",
          "maxLength": 2048,
          "description": "Optional package page URL (npmjs.com/package/…, pypi.org/project/…, crates.io/crates/…) for the payload_safety path."
        },
        "quoted_amount": {
          "type": "number",
          "description": "Quoted amount in USDC the wallet is about to pay.",
          "exclusiveMinimum": 0
        },
        "tool_category": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Optional category of the tool/service being bought (e.g. data_lookup, market_data, inference, compute). Selects the v1 default cap when policy_cap_usdc is omitted; when omitted entirely the cap table's \"default\" cap applies."
        },
        "payment_header": {
          "type": "string",
          "description": "Base64 X-PAYMENT EIP-3009 payload (standard rail) for $0.005 USDC on Base."
        },
        "wallet_address": {
          "type": "string",
          "description": "Agent wallet address (informational)."
        },
        "payment_tx_hash": {
          "type": "string",
          "description": "Base USDC tx hash (sovereign rail) paying $0.005 to the canonical SML receiver."
        },
        "policy_cap_usdc": {
          "type": "number",
          "description": "Optional caller policy cap in USDC; overrides the v1 default cap table for price_sanity.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
  • omnigate_runtime_execute unknown never probed

    OMNIGATE Runtime (PAID, USDC). Run ONE JavaScript script that calls many SML tools, in one round trip, instead of one model turn per tool call. The script is the body of an async function: `const r = await sml.call("<route-id>", { query: {...} }); return r.data;`. Available inside: sml.call, sml.tools.search, sml.tools.get, sml.budget, sml.sleep, sml.log, sml.input. Every call is metered at its live registry price against budget_usdc, charged only on upstream 2xx, and tagged with source + response sha256; a failed upstream throws TruthError (nothing charged, nothing substituted). Unused budget is returned as credit. Returns result, per-call provenance, billing and an Ed25519-signed receipt id. Without payment it returns the x402 challenge (amount = budget). Pay with payment_header (Base USDC, x402 v2), credit_token (smlrt_…), or arc_auth_id (Arc escrow, when enabled). Sandbox: no network except sml.call, no fs, 32MB, 20s CPU, 120s wall (sync).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "mode": {
          "enum": [
            "sync",
            "async"
          ],
          "type": "string",
          "default": "sync",
          "description": "sync waits for the result (120s wall); async returns run_id to poll /runtime/runs/{id}."
        },
        "input": {
          "type": "object",
          "description": "JSON object exposed to the script as sml.input.",
          "additionalProperties": {}
        },
        "script": {
          "type": "string",
          "maxLength": 65536,
          "description": "JavaScript async-function body. Use await; return the final result."
        },
        "capsule_id": {
          "type": "string",
          "maxLength": 120,
          "description": "Run a published capsule instead of a script (e.g. cap_name@1 or cap_name@latest)."
        },
        "arc_auth_id": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$",
          "description": "Arc AuthCaptureEscrow authorization id (maxAmount ≥ budget, expiry ≤ 24h)."
        },
        "budget_usdc": {
          "type": "string",
          "default": "0.05",
          "pattern": "^\\d+(\\.\\d{1,6})?$",
          "description": "Hard spending cap for the whole run in USDC (min 0.01, max 25)."
        },
        "credit_token": {
          "type": "string",
          "maxLength": 100,
          "description": "Runtime credit token (smlrt_…) returned by an earlier run."
        },
        "payment_header": {
          "type": "string",
          "maxLength": 8192,
          "description": "Base64 x402 v2 payment payload for exactly budget_usdc USDC on Base (from the challenge)."
        }
      },
      "additionalProperties": false
    }
    arguments 52 lines
  • omnigate_runtime_receipt unknown never probed

    OMNIGATE Runtime receipt (FREE). Returns a run receipt — script sha256, payer, rail, payment tx, every upstream call with request/response hashes and charges, outcome — signed with Ed25519 and hash-chained to the previous receipt, plus a verification of signature, body hash and chain link. Use it to prove what an agent ran and paid for.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "receipt_id"
      ],
      "properties": {
        "receipt_id": {
          "type": "string",
          "pattern": "^rcpt_[A-Za-z0-9_-]{8,80}$",
          "description": "Receipt id from a runtime run (rcpt_…)."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6aca15fc3f738044.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6aca15fc3f738044/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6aca15fc3f738044/badge.svg)](https://brick.blue/agent/6aca15fc3f738044?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.