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

qed.bot register

listed under this name in a public catalogue; the server gives only its address, qed.bot

https://qed.bot

Registry code: f6e3c966c189ad20

api record

A register of claims of AI work in mathematics, and of the evidence behind each. This endpoint reads the graph. Verifying or submitting a proof or a construction runs its author's code, so those tools are offered only by the local server: python -m mcp_server.server. check_proof has qed.bot rebuild a Lean file for credits, with an API key from https://qed.bot/check.

endpoint
https://qed.bot/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 qed.bot register live?
Yes — it answered the hub's last check (checked 35m ago). It answered 100% of checks over the last 30 days.
Is qed.bot register free to use?
Yes — the hub reached it with no key and no payment.
What tools does qed.bot register have?
16 tools: registry_positions, get_formalisation, get_target, list_collections, open_problems, list_systems, search_statements, get_statement, ….
Is qed.bot register 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
579ms

last good check

priced tools
0

of 16 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 16 tools
3 open 13 never probed 3 of 16 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.

  • benchmarks open 35m ago

    Benchmarks as sets of statements, with how many members already carry public AI work: a contamination figure rather than a study.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "include_members": {
          "type": "boolean",
          "default": false
        }
      }
    }
    arguments 9 lines
  • compare_registries open 35m ago

    Results recorded by more than one registry, and how the positions differ. A disagreement is a difference of judgement about who did the mathematics; a gap is one registry holding stronger evidence than another; a lead is a proof somebody else records that this register has not rebuilt.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25
        },
        "finding": {
          "enum": [
            "any",
            "disagreement",
            "gap",
            "lead",
            "agreement"
          ],
          "type": "string",
          "default": "any"
        },
        "registry": {
          "type": "string",
          "description": "Restrict to results this registry holds"
        }
      }
    }
    arguments 24 lines
  • disclosure open 35m ago

    Announcements of results, graded for how much of what they claim can be inspected: whether each result is named, written up, and published with a checkable artifact.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "org": {
          "type": "string",
          "description": "Restrict to one organisation"
        }
      }
    }
    arguments 9 lines
  • registry_positions unknown never probed

    Every registry's position on one result, this register included, with each one's own label preserved beside the bucket it was placed in.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Node id, e.g. erdos:346"
        }
      }
    }
    arguments 12 lines
  • get_formalisation unknown never probed

    One declaration in full: its sources, related formalisations, main results, the results held here it joins and on what key, Palomar's registrations of it, and any contradiction between what it declares and what a rebuild found.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "owner/repo for a root declaration, owner/repo/path, or its GitHub URL"
        }
      }
    }
    arguments 12 lines
  • get_target unknown never probed

    Everything the register holds about one target: the record history with who held each value and when, the graded claims, and any check run here.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Canonical id, e.g. capset:dimension-8"
        }
      }
    }
    arguments 12 lines
  • list_collections unknown never probed

    The collections held, with counts of statements, formalisations and AI activity.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • open_problems unknown never probed

    Statements not recorded as solved, most valuable prize first. Use formalised_only to restrict to those a prover could attempt directly.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25
        },
        "min_prize": {
          "type": "integer",
          "default": 0
        },
        "collection": {
          "type": "string"
        },
        "formalised_only": {
          "type": "boolean"
        }
      }
    }
    arguments 19 lines
  • list_systems unknown never probed

    Track record per AI system, computed from recorded claims. Not a benchmark: which statements attract attention has little to do with how hard they are.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "Restrict to one system"
        },
        "limit": {
          "type": "integer",
          "default": 25
        }
      }
    }
    arguments 13 lines
  • search_statements unknown never probed

    Search the register of mathematical statements. Returns summaries with formal status, prizes, and how much AI work is recorded against each.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25
        },
        "query": {
          "type": "string",
          "description": "Text to match in id, title, collection or tags"
        },
        "has_prize": {
          "type": "boolean"
        },
        "collection": {
          "type": "string",
          "description": "Restrict to one collection"
        },
        "has_ai_claim": {
          "type": "boolean"
        },
        "formal_status": {
          "enum": [
            "open",
            "solved",
            "mixed",
            "unclassified"
          ],
          "type": "string"
        },
        "verified_only": {
          "type": "boolean",
          "description": "Only statements with a proof recompiled here"
        }
      }
    }
    arguments 36 lines
  • get_statement unknown never probed

    Everything the register holds about one statement: formalisations, cited proofs, recompilation results, graded claims, relations and aliases.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Canonical id or any alias, e.g. erdos:707"
        }
      }
    }
    arguments 12 lines
  • check_proof unknown never probed

    Have qed.bot rebuild a Lean file at its commit and read what every theorem in it depends on, under the admission rules every stranger's file is held to. Costs one credit, or two for a private check; buy credits and make an API key at https://qed.bot/check, and send it as Authorization: Bearer qed_.... Returns at once with the check queued; call get_check until it is done, which takes minutes. A file already checked in public is returned free, and a check that stops on qed.bot's side is refunded.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "GitHub blob URL of the .lean file, at a full commit"
        },
        "private": {
          "type": "boolean",
          "default": false,
          "description": "Only you can see the result (2 credits)"
        },
        "theorem": {
          "type": "string",
          "description": "The theorem it proves, which must be declared"
        }
      }
    }
    arguments 21 lines
  • get_check unknown never probed

    A paid check's status and verdict, by the id check_proof returned. Needs the same API key for a private check.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "description": "The check's id"
        }
      }
    }
    arguments 12 lines
  • search_formalisations unknown never probed

    Every formalization.yaml the register has read, with what each declares about its own axioms, unproved goals, assumed literature, automation and review, and who has checked it: this register, Palomar, or nobody independent of its authors.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "flag": {
          "enum": [
            "alignment",
            "axioms",
            "comparator",
            "contradicted",
            "divergences",
            "literature",
            "original",
            "unproved"
          ],
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "default": 25
        },
        "query": {
          "type": "string",
          "description": "Text to match in name, repository, path, authors or models"
        },
        "method": {
          "enum": [
            "autonomous",
            "agent",
            "copilot",
            "manual",
            "other"
          ],
          "type": "string"
        },
        "review": {
          "enum": [
            "peer-reviewed",
            "author-verified",
            "agent-reviewed",
            "self-assessed",
            "unchecked",
            "other",
            "not stated"
          ],
          "type": "string"
        },
        "held_only": {
          "type": "boolean",
          "description": "Only declarations joined to a result held here"
        },
        "checked_by": {
          "enum": [
            "Palomar",
            "qed.bot",
            "none"
          ],
          "type": "string",
          "description": "Who checked it; none for declarations nobody independent has checked"
        }
      }
    }
    arguments 61 lines
  • list_evaluators unknown never probed

    The object checkers available, what each establishes, what an artifact must look like, and which targets have been checked with it. Read this before calling submit_construction, which only the local server offers.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_targets unknown never probed

    Search the targets: quantities with a direction and a record history, where AI work moved a bound or produced a better object rather than settling a statement.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25
        },
        "query": {
          "type": "string",
          "description": "Text to match in id, name, collection or tags"
        },
        "standing": {
          "enum": [
            "record",
            "matched",
            "superseded",
            "below",
            "unstated"
          ],
          "type": "string"
        },
        "collection": {
          "type": "string"
        },
        "checked_only": {
          "type": "boolean",
          "description": "Only targets whose object was rebuilt here"
        },
        "held_by_machine": {
          "type": "boolean",
          "description": "Only where the leading record is a machine's"
        }
      }
    }
    arguments 34 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 f6e3c966c189ad20.

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