_ registry / mcp http-sse · checked 10m ago

Sortition Knowledge

https://mcp.sortition.dk

Registry code: dd9bd0a256d16c98

api record

Sortition Knowledge provides research and source material about:

- sortition and random selection in democracy

endpoint
https://mcp.sortition.dk
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
0 · newcomer
_ is it live, free and safe measured by this hub
Is Sortition Knowledge live?
Yes — it answered the hub's last check (checked 10m ago). It answered 98% of checks over the last 30 days.
Is Sortition Knowledge free to use?
Yes — the hub reached it with no key and no payment.
What tools does Sortition Knowledge have?
4 tools: search_knowledge, get_document_page, list_documents, get_service_overview.
Is Sortition Knowledge 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.2%

90 days 98.8%· all time 98.8%

latency
622ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 324 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
  • search research on sortition and citizens assemblies
  • list source documents
  • read a full page of a source document
takes → gives
text → text, documents
tools
4 reads
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • list_documents reads open 21h ago

    List the source documents currently available in the Sortition knowledge base.

    mcp-tool

    {
      "type": "object",
      "title": "list_documentsArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_service_overview reads open 21h ago

    Describe the purpose, scope and recommended use of the Sortition Knowledge MCP service.

    mcp-tool

    {
      "type": "object",
      "title": "get_service_overviewArguments",
      "properties": {}
    }
    arguments 5 lines
  • search_knowledge reads unknown 5h ago

    Semantically search the Sortition knowledge base. Use this for questions about sortition, citizens' assemblies, citizens' chambers, democratic institutions and related reforms. Returns relevant source excerpts with document name, page and score.

    mcp-tool

    {
      "type": "object",
      "title": "search_knowledgeArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 5
        },
        "query": {
          "type": "string",
          "title": "Query"
        }
      }
    }
    arguments 18 lines
  • get_document_page reads unknown 21h ago

    Retrieve the complete text of one page from a PDF source document. Use this after search_knowledge() when more context or source verification is needed.

    mcp-tool

    {
      "type": "object",
      "title": "get_document_pageArguments",
      "required": [
        "document",
        "page"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "title": "Page"
        },
        "document": {
          "type": "string",
          "title": "Document"
        }
      }
    }
    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 dd9bd0a256d16c98.

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

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.