_ registry / mcp streamable-http · checked 2h ago

riskrouter

https://api.riskrouter.eu

Registry code: 68e58e4d6d328740

api record

RiskRouter keeps a public, append-only log of SHA-256 digests of regulated decisions, and proofs anyone can check without us. Records never come here: hash your own salted record and send only the digest (see https://riskrouter.eu/spec#records). Recording needs the operator's key; reading the log does not. This server prices nothing and offers no insurance.

endpoint
https://api.riskrouter.eu/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 riskrouter live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is riskrouter free to use?
Yes — the hub reached it with no key and no payment.
What tools does riskrouter have?
8 tools: get_chain, record_evidence, get_consistency_proof, get_inclusion_proof, get_usage, get_checkpoint, get_evidence_head, get_ledger_attestation.
Is riskrouter 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
98.1%

90 days 98.7%· all time 98.7%

latency
280ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 394 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • record a decision record digest
  • get an inclusion proof from the log
  • get the signed log checkpoint
takes → gives
text → data
tools
6 reads1 changes data
_ 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 8 tools
4 open 4 never probed 4 of 8 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.

  • get_usage reads open 24h ago

    How much is recorded, and by how many keys that are not ours. Counts only, nothing about anyone.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_checkpoint reads open 24h ago

    The log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_evidence_head reads open 24h ago

    The current signed head of the evidence log: tree size, Merkle root and signature. Save it: any later head must be consistent with it.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_ledger_attestation reads open 6h ago

    The signed head hash of the hash-chained audit ledger of recorded quotes.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_chain unknown 2h ago

    The log's signed statement of one completeness chain as of the current head: its length and, for each position, the leaf, the time and the digest. A position nobody showed you is a record left out.

    mcp-tool

    {
      "type": "object",
      "required": [
        "chain_tag"
      ],
      "properties": {
        "to": {
          "type": "integer",
          "minimum": 0,
          "description": "Optional: the last position to list."
        },
        "from": {
          "type": "integer",
          "minimum": 0,
          "description": "Optional: the first position to list."
        },
        "chain_tag": {
          "type": "string",
          "pattern": "^[0-9a-f]{64}$",
          "description": "The chain's 64-hex tag."
        }
      }
    }
    arguments 23 lines
  • record_evidence changes data unknown never probed

    Record the SHA-256 of a decision record you keep yourself, so it can later be shown to be unchanged. Send the digest and a short kind, never the record. Needs your RiskRouter key in the Authorization header of the MCP connection. Entries are permanent.

    mcp-tool

    {
      "type": "object",
      "required": [
        "record_digest",
        "kind"
      ],
      "properties": {
        "kind": {
          "type": "string",
          "pattern": "^[a-z0-9][a-z0-9.-]{0,39}$",
          "description": "A short tag such as ai.decision."
        },
        "chain_seq": {
          "type": "integer",
          "minimum": 1,
          "description": "Optional, with chain_tag: this record's position in its chain, from 1."
        },
        "chain_tag": {
          "type": "string",
          "pattern": "^[0-9a-f]{64}$",
          "description": "Optional: the completeness chain this record belongs to (64 hex characters derived from a secret you keep)."
        },
        "record_digest": {
          "type": "string",
          "pattern": "^[0-9a-f]{64}$",
          "description": "SHA-256 of your salted record, lowercase hex. Never the record itself."
        }
      }
    }
    arguments 29 lines
  • get_consistency_proof reads unknown 6h ago

    Proof that the tree at size first is a prefix of the tree at size second (or now): the log never rewrote history.

    mcp-tool

    {
      "type": "object",
      "required": [
        "first"
      ],
      "properties": {
        "first": {
          "type": "integer",
          "minimum": 0,
          "description": "A tree size you hold a head for."
        },
        "second": {
          "type": "integer",
          "minimum": 0,
          "description": "Optional: a later tree size."
        }
      }
    }
    arguments 18 lines
  • get_inclusion_proof reads unknown 6h ago

    Proof that the entry at leaf_index is in the tree, optionally at a given tree_size. Checkable offline with the public verifier.

    mcp-tool

    {
      "type": "object",
      "required": [
        "leaf_index"
      ],
      "properties": {
        "tree_size": {
          "type": "integer",
          "minimum": 0,
          "description": "Optional: the tree size to prove against."
        },
        "leaf_index": {
          "type": "integer",
          "minimum": 0,
          "description": "Position of the entry in the log."
        }
      }
    }
    arguments 18 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 68e58e4d6d328740.

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