_ registry / mcp streamable-http · checked 59m ago

iomarkets-tech

https://iomarkets.tech

Registry code: f7de1ed0829dc6ae

api record

Tools for IoMarkets.tech, open tools for capital-markets plumbing. list_corporate_actions and holdings_calendar give dividends, splits and mergers of US-listed companies from their SEC filings; get_corporate_action adds the seev.031 message. check_token_contract says whether a token contract is the issuer’s real tokenized fund or security (the Tokenized Asset Map). validate_message checks an ISO 20022 message (pacs.008, pacs.009, pain.001, camt.053, seev.031) against the official schema and business rules; explain_issue says how to fix each problem; list_samples and get_sample give valid and…

endpoint
https://iomarkets.tech/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is iomarkets-tech live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is iomarkets-tech free to use?
Yes — the hub reached it with no key and no payment.
What tools does iomarkets-tech have?
23 tools: verify_execution_report, list_tokenized_assets, get_tokenized_asset, verify_asset_with_issuer, holdings_calendar, get_corporate_action, token_corporate_actions, get_overview, ….
Is iomarkets-tech 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
100%

90 days 100%· all time 100%

latency
224ms

last good check

priced tools
0

of 23 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 23 tools
2 open 21 never probed 2 of 23 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.

  • explain_issue open 59m ago

    What a Test Bench issue code (such as IBAN_CHECKSUM, BALANCE_MISMATCH or OUT_OF_ORDER) means and how to fix it. Without a code, lists every code.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "code": {
          "type": "string",
          "description": "The issue code from a report."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • explain_execution_request open 59m ago

    Exactly how to call POST https://api.iomarkets.tech/v1/proof/execution, the paid best-execution audit: the body (pair, one of BTC-USDC, ETH-USDC, SOL-USDC, and fills: ts, fill_price, qty, side), the limits (fills per call, how old a fill may be, how close the market trade must be), the price, what comes back, and the answers that are not charged (400 for a bad body or an unsupported pair, 422 when no fill matches a trade). Give a draft body to check it with the API's own validation first. Read from the API's code; this tool calls nothing and pays nothing.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "body": {
          "type": "string",
          "description": "A draft request body as JSON text, { \"pair\": \"BTC-USDC\", \"fills\": [...] }, to check before paying (optional)."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • verify_execution_report unknown never probed

    Check the whole JSON that POST https://api.iomarkets.tech/v1/proof/execution returned ({ audit, summary, attestation }): that the ed25519 signature matches the published IoMarkets key, that its USDC payment is confirmed on Algorand mainnet (a public indexer IoMarkets does not run), that the rows hash to the signed audit_sha256, and that every row and the summary recompute with the API's own scoring, against the last trade and against the arrival mid (side-aware cost, qty-weighted averages, spread, matched and unmatched fills). The same checks as the page at https://iomarkets.tech/execution-check. Returns each check, and the recomputed summary as structured data.

    mcp-tool

    {
      "type": "object",
      "required": [
        "report"
      ],
      "properties": {
        "report": {
          "type": "string",
          "description": "The response body as JSON text, exactly as received: { \"audit\": [...], \"summary\": {...}, \"attestation\": { \"payload\": {...}, \"signature\": \"…\" } }."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_tokenized_assets unknown never probed

    The securities in the Tokenized Asset Map with their identifiers (FIGI, ISIN where the issuer gives it) and the chains they are tokenized on. Optionally filter by issuer, name, symbol, ticker, ISIN or FIGI.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Filter text (optional)."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_tokenized_asset unknown never probed

    One Asset Map entry in full: the security, every token contract chain by chain, the issuer sources each comes from, and whether its IoMarkets signature verifies.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "franklin-fobxx",
            "franklin-onchain-lux-ib",
            "franklin-onchain-lux-ab-ddis",
            "franklin-onchain-sg-usd-st",
            "ondo-ousg",
            "ondo-usdy",
            "superstate-ustb",
            "superstate-uscc",
            "superstate-cushy",
            "superstate-vbdc",
            "superstate-fwdi",
            "circle-usyc",
            "spiko-ustbl",
            "spiko-eutbl",
            "spiko-uktbl",
            "spiko-spkcc",
            "spiko-eurspkcc",
            "spiko-safo",
            "spiko-eursafo",
            "spiko-gbpsafo",
            "spiko-chfsafo",
            "xstocks-strcx",
            "xstocks-mstrx",
            "xstocks-crclx",
            "xstocks-tslax",
            "xstocks-spcxx",
            "xstocks-spyx",
            "xstocks-googlx",
            "xstocks-qqqx",
            "xstocks-nvdax",
            "xstocks-sndkx",
            "xstocks-mux",
            "xstocks-coinx",
            "xstocks-aaplx",
            "xstocks-skhyx",
            "xstocks-gldx",
            "xstocks-intcx",
            "xstocks-metax",
            "xstocks-soxlx",
            "xstocks-hoodx",
            "xstocks-amznx",
            "xstocks-msftx",
            "xstocks-avgox",
            "xstocks-mrvlx",
            "xstocks-amdx",
            "xstocks-tsmx",
            "xstocks-orclx",
            "xstocks-ewyx",
            "xstocks-jaaax",
            "xstocks-tqqqx",
            "xstocks-bmnrx",
            "ondo-stocks-aaplon",
            "ondo-stocks-amdon",
            "ondo-stocks-amznon",
            "ondo-stocks-avgoon",
            "ondo-stocks-bmnron",
            "ondo-stocks-coinon",
            "ondo-stocks-crclon",
            "ondo-stocks-ewyon",
            "ondo-stocks-gldon",
            "ondo-stocks-googlon",
            "ondo-stocks-hoodon",
            "ondo-stocks-intcon",
            "ondo-stocks-jaaaon",
            "ondo-stocks-metaon",
            "ondo-stocks-mrvlon",
            "ondo-stocks-msfton",
            "ondo-stocks-mstron",
            "ondo-stocks-muon",
            "ondo-stocks-nvdaon",
            "ondo-stocks-orclon",
            "ondo-stocks-qqqon",
            "ondo-stocks-skhyon",
            "ondo-stocks-sndkon",
            "ondo-stocks-spyon",
            "ondo-stocks-strcon",
            "ondo-stocks-tqqqon",
            "ondo-stocks-tslaon",
            "ondo-stocks-tsmon",
            "ondo-stocks-soxlon",
            "ondo-stocks-spcxon"
          ],
          "type": "string",
          "description": "The entry id, from list_tokenized_assets."
        }
      },
      "additionalProperties": false
    }
    arguments 96 lines
  • verify_asset_with_issuer unknown never probed

    Fetch the issuer's own sources for one Asset Map entry now (its contracts page, its public API, or its stellar.toml) and confirm every listed contract is still there, so trust needn't rest on IoMarkets.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "franklin-fobxx",
            "franklin-onchain-lux-ib",
            "franklin-onchain-lux-ab-ddis",
            "franklin-onchain-sg-usd-st",
            "ondo-ousg",
            "ondo-usdy",
            "superstate-ustb",
            "superstate-uscc",
            "superstate-cushy",
            "superstate-vbdc",
            "superstate-fwdi",
            "circle-usyc",
            "spiko-ustbl",
            "spiko-eutbl",
            "spiko-uktbl",
            "spiko-spkcc",
            "spiko-eurspkcc",
            "spiko-safo",
            "spiko-eursafo",
            "spiko-gbpsafo",
            "spiko-chfsafo",
            "xstocks-strcx",
            "xstocks-mstrx",
            "xstocks-crclx",
            "xstocks-tslax",
            "xstocks-spcxx",
            "xstocks-spyx",
            "xstocks-googlx",
            "xstocks-qqqx",
            "xstocks-nvdax",
            "xstocks-sndkx",
            "xstocks-mux",
            "xstocks-coinx",
            "xstocks-aaplx",
            "xstocks-skhyx",
            "xstocks-gldx",
            "xstocks-intcx",
            "xstocks-metax",
            "xstocks-soxlx",
            "xstocks-hoodx",
            "xstocks-amznx",
            "xstocks-msftx",
            "xstocks-avgox",
            "xstocks-mrvlx",
            "xstocks-amdx",
            "xstocks-tsmx",
            "xstocks-orclx",
            "xstocks-ewyx",
            "xstocks-jaaax",
            "xstocks-tqqqx",
            "xstocks-bmnrx",
            "ondo-stocks-aaplon",
            "ondo-stocks-amdon",
            "ondo-stocks-amznon",
            "ondo-stocks-avgoon",
            "ondo-stocks-bmnron",
            "ondo-stocks-coinon",
            "ondo-stocks-crclon",
            "ondo-stocks-ewyon",
            "ondo-stocks-gldon",
            "ondo-stocks-googlon",
            "ondo-stocks-hoodon",
            "ondo-stocks-intcon",
            "ondo-stocks-jaaaon",
            "ondo-stocks-metaon",
            "ondo-stocks-mrvlon",
            "ondo-stocks-msfton",
            "ondo-stocks-mstron",
            "ondo-stocks-muon",
            "ondo-stocks-nvdaon",
            "ondo-stocks-orclon",
            "ondo-stocks-qqqon",
            "ondo-stocks-skhyon",
            "ondo-stocks-sndkon",
            "ondo-stocks-spyon",
            "ondo-stocks-strcon",
            "ondo-stocks-tqqqon",
            "ondo-stocks-tslaon",
            "ondo-stocks-tsmon",
            "ondo-stocks-soxlon",
            "ondo-stocks-spcxon"
          ],
          "type": "string",
          "description": "The entry id."
        }
      },
      "additionalProperties": false
    }
    arguments 96 lines
  • holdings_calendar unknown never probed

    For a list of holdings (tickers, CIKs or FIGIs), every ex-date, record date, payment date and effective date in one week, day by day. The week holding `day`, Monday to Sunday; this week by default. Ends with an iCalendar (webcal) subscription URL for those holdings, to give the user for their calendar app.

    mcp-tool

    {
      "type": "object",
      "required": [
        "holdings"
      ],
      "properties": {
        "day": {
          "type": "string",
          "description": "Any day in the week, YYYY-MM-DD (optional; today by default)."
        },
        "holdings": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Tickers, SEC CIKs or FIGIs."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_corporate_action unknown never probed

    One event in full: every date and term, the filing and the sentence or table row it came from, tokenized versions in the Asset Map, and the event as an ISO 20022 seev.031.001.14 notification (checked by the Test Bench).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The event id, from list_corporate_actions or holdings_calendar."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • token_corporate_actions unknown never probed

    For a token contract that the Asset Map lists as a tokenized stock or ETF (such as an xStock): the security it tracks, and that security's dividends, splits and mergers from the corporate actions feed, each with what it does to the token. Answers 'I hold this token; what is coming?' in one call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "chain",
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "ethereum",
            "polygon",
            "arbitrum",
            "avalanche",
            "base",
            "bnb",
            "mantle",
            "plume",
            "sei",
            "tempo",
            "optimism",
            "ink",
            "monad",
            "hyperevm",
            "xlayer",
            "etherlink",
            "arc",
            "robinhood",
            "solana",
            "stellar",
            "aptos",
            "sui",
            "xrpl",
            "noble",
            "ton",
            "tron",
            "starknet"
          ],
          "type": "string",
          "description": "The chain the token is on."
        },
        "address": {
          "type": "string",
          "description": "The token contract."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • get_overview unknown never probed

    What IoMarkets.tech is and what is built: the ISO 20022 Test Bench, the Data API (market data for AI agents, paid per request over x402), the main pages, and what comes next.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_samples unknown never probed

    The Test Bench sample library: a valid message of each type and broken ones, each with the issue code it raises. Use get_sample for the XML.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "message": {
          "enum": [
            "pacs.008.001.08",
            "pacs.009.001.08",
            "pacs.002.001.10",
            "pacs.004.001.09",
            "pain.001.001.09",
            "camt.053.001.08",
            "camt.054.001.08",
            "seev.031.001.14"
          ],
          "type": "string",
          "description": "Only samples of this message type (optional)."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_sample unknown never probed

    The XML of one sample message from list_samples, to use as a starting point or in tests. Every party and account in it is made up.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "pacs.008-valid",
            "pacs.009-valid",
            "pacs.002-valid",
            "pacs.004-valid",
            "pain.001-valid",
            "camt.053-valid",
            "camt.054-valid",
            "seev.031-valid",
            "pacs.008-in-envelope",
            "pacs.008-missing-charge-bearer",
            "pacs.008-msgid-too-long",
            "pacs.008-lowercase-currency",
            "pacs.008-out-of-order",
            "pacs.008-impossible-date",
            "pacs.008-unknown-element",
            "pacs.008-bad-uetr",
            "pacs.008-unclosed-tag",
            "pacs.008-iban-checksum",
            "pacs.008-bic-country",
            "pacs.008-lei-checksum",
            "pacs.008-count-mismatch",
            "pacs.008-no-settlement-date",
            "pacs.008-yen-decimals",
            "pacs.008-fx-without-rate",
            "pacs.009-total-mismatch",
            "pacs.009-cover-without-reimbursement",
            "pain.001-control-sum",
            "pain.001-cheque-with-account",
            "camt.053-balance-mismatch",
            "camt.053-entry-count",
            "seev.031-isin-check-digit",
            "seev.031-paid-before-record-date",
            "seev.031-two-statuses",
            "seev.031-dividend-without-cash",
            "pacs.002-status-too-long",
            "pacs.002-accepted-but-rejected",
            "pacs.002-narrative-without-text",
            "pacs.002-original-group-twice",
            "pacs.004-missing-returned-amount",
            "pacs.004-total-mismatch",
            "pacs.004-charges-without-instructed-amount",
            "pacs.004-group-return-with-transactions",
            "pacs.004-fx-without-rate",
            "camt.054-credit-spelled-out",
            "camt.054-entry-sum",
            "camt.054-two-paginations",
            "camt.054-empty-bank-code",
            "pacs.008-unsupported-version"
          ],
          "type": "string",
          "description": "The sample id, from list_samples."
        }
      },
      "additionalProperties": false
    }
    arguments 63 lines
  • check_token_contract unknown never probed

    Check a token contract against the Tokenized Asset Map: is it the issuer's own contract for a tokenized fund or security on that chain? Verdicts: official, other-chain (the address is listed, but on another chain), impostor (a listed symbol on this chain, a different contract), unknown (not in the map, which says nothing either way).

    mcp-tool

    {
      "type": "object",
      "required": [
        "chain",
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "ethereum",
            "polygon",
            "arbitrum",
            "avalanche",
            "base",
            "bnb",
            "mantle",
            "plume",
            "sei",
            "tempo",
            "optimism",
            "ink",
            "monad",
            "hyperevm",
            "xlayer",
            "etherlink",
            "arc",
            "robinhood",
            "solana",
            "stellar",
            "aptos",
            "sui",
            "xrpl",
            "noble",
            "ton",
            "tron",
            "starknet"
          ],
          "type": "string",
          "description": "The chain the contract is on."
        },
        "symbol": {
          "type": "string",
          "description": "The symbol the token shows (optional), to catch impostors."
        },
        "address": {
          "type": "string",
          "description": "The contract: 0x address, Solana mint, Stellar CODE:ISSUER, Aptos/Sui type tag, …"
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
  • list_corporate_actions unknown never probed

    Corporate actions of US-listed companies from their own SEC EDGAR filings (8-Ks of US companies, 6-Ks of foreign private issuers): cash dividends (amount in the stated currency, per share or per ADS, ex, record and payment dates), stock splits, reverse splits and completed mergers (cash or shares per share). Filter by holdings (tickers, CIKs or FIGIs), by days (any of an event's dates between from and to) and by type. Each event links its filing and the sentence or table row it was read from. Also gives the iCalendar subscription URL for the same holdings and types (calendarUrl in structuredContent).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "Last day, YYYY-MM-DD (optional)."
        },
        "from": {
          "type": "string",
          "description": "First day, YYYY-MM-DD (optional)."
        },
        "types": {
          "type": "array",
          "items": {
            "enum": [
              "dividend",
              "split",
              "reverse-split",
              "merger"
            ],
            "type": "string"
          },
          "description": "Kinds of event (optional)."
        },
        "holdings": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Tickers, SEC CIKs or FIGIs (optional; none means every company)."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • get_roadmap unknown never probed

    What IoMarkets.tech has built and is building next, in the same words as iomarkets.org/roadmap.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • estimate_data_api_cost unknown 59m ago

    What a monthly volume of Data API calls costs at the per-call x402 prices, against the indicative subscription plans. Give calls per month for each route; routes left out count as zero.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "candles": {
          "type": "number",
          "description": "Calls a month to /v1/candles (Candles)."
        },
        "proof_price": {
          "type": "number",
          "description": "Calls a month to /v1/proof/price (Price proof)."
        },
        "signal_vwap": {
          "type": "number",
          "description": "Calls a month to /v1/signal/vwap (VWAP signal)."
        },
        "proof_execution": {
          "type": "number",
          "description": "Calls a month to /v1/proof/execution (Execution proof)."
        },
        "signal_imbalance": {
          "type": "number",
          "description": "Calls a month to /v1/signal/imbalance (Order imbalance)."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • get_guide unknown never probed

    Step-by-step instructions, with the exact button names, for one task on iomarkets.tech (checking a message, CI, verifying a proof, calling the Data API…). Without a task, lists the tasks.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "task": {
          "enum": [
            "look-around",
            "check-message",
            "try-samples",
            "bench-ci",
            "check-token",
            "holdings-week",
            "token-events",
            "verify-proof",
            "check-execution-report",
            "data-api",
            "console",
            "own-assistant"
          ],
          "type": "string",
          "description": "Which task. Leave out to list them all."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • explain_term unknown never probed

    A plain-English meaning of a word used on the site (ISO 20022, schema, IBAN, BIC, LEI, ISIN, UETR, CBPR+, x402, signed proof, MCP…) or of an ISO 20022 XML tag abbreviation such as GrpHdr, CdtrAcct or IntrBkSttlmAmt. Without a term, lists the words.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "term": {
          "type": "string",
          "description": "The word or tag to explain."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_messages unknown never probed

    The ISO 20022 message types and versions the Test Bench checks, with what each is for.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • validate_message unknown never probed

    Check one ISO 20022 XML message (pacs.008.001.08, pacs.009.001.08, pacs.002.001.10, pacs.004.001.09, pain.001.001.09, camt.053.001.08, camt.054.001.08 or seev.031.001.14) against the official base schema, then business rules (check digits, totals, cross-element rules, market practice). Returns valid or not, and every problem with its line, element path, stable code and a plain reason. The message type is read from the namespace. The message is checked and not stored. Same code as https://iomarkets.tech/test-bench.

    mcp-tool

    {
      "type": "object",
      "required": [
        "xml"
      ],
      "properties": {
        "xml": {
          "type": "string",
          "description": "The whole message, as XML text. A <Document> inside an envelope with an AppHdr is fine."
        },
        "message": {
          "enum": [
            "pacs.008.001.08",
            "pacs.009.001.08",
            "pacs.002.001.10",
            "pacs.004.001.09",
            "pain.001.001.09",
            "camt.053.001.08",
            "camt.054.001.08",
            "seev.031.001.14"
          ],
          "type": "string",
          "description": "Check as this message type instead of the one its namespace names (optional)."
        },
        "schema_only": {
          "type": "boolean",
          "description": "Skip business rules (optional, default false)."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • list_data_endpoints unknown never probed

    The Data API routes at https://api.iomarkets.tech, what each returns and its price per call in USDC, with how an AI agent pays (x402 on Algorand mainnet, no account).

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_api_status unknown never probed

    Whether the Data API at https://api.iomarkets.tech is answering right now, from its /health check.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • verify_proof unknown never probed

    Check a signed proof (the { payload, signature } JSON a Data API proof route returns): that the ed25519 signature matches the published IoMarkets key, and that its USDC payment is confirmed on Algorand mainnet (looked up on a public indexer IoMarkets does not run).

    mcp-tool

    {
      "type": "object",
      "required": [
        "proof"
      ],
      "properties": {
        "proof": {
          "type": "string",
          "description": "The proof as JSON text: { \"payload\": {…}, \"signature\": \"…\" }."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it 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 f7de1ed0829dc6ae.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f7de1ed0829dc6ae/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/f7de1ed0829dc6ae/badge.svg)](https://brick.blue/agent/f7de1ed0829dc6ae?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 know
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.