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

boltclaw-docs

https://boltclaw.ai

Registry code: 08d0393090c88742

api record

Read-only documentation for the Bolt Claw API. No API key is needed and nothing here changes anything. Call `search` with a few words to find the pages that cover a subject, then `fetch` with an id from the results to read one in full. The whole documentation is also one markdown file at https://boltclaw.ai/llms-full.txt, and the index an assistant should read first is https://boltclaw.ai/llms.txt. To DO anything in a Bolt Claw workspace, use the hosted MCP server instead - it needs the person's own credentials and is described on the MCP page.

endpoint
https://boltclaw.ai/docs/mcp-server
door code
65521ca38721013d
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 boltclaw-docs live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is boltclaw-docs free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does boltclaw-docs have?
2 tools: search, fetch.
Is boltclaw-docs 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
333ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 auth-required 1 never probed 1 of 2 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.

  • fetch auth-required 2h ago

    Read one documentation page in full, as markdown. The id is what `search` returns, which is the page's path without /docs/ - for example `authentication` or `api/pages`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "A page id from `search`, such as \"errors\" or \"api/posts\"."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • search unknown 2h ago

    Find documentation pages about a subject. Returns an id, a title, a URL and a matching line for each hit, best first. Pass the id to `fetch` to read the page.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 25,
      "minimum": 1,
      "description": "How many results to return. Defaults to 8."
    },
    "query": {
      "type": "string",
      "description": "What to look for, in a few words. Matched against titles, sections and text."
    }
  },
  "additionalProperties": false
}
    arguments 20 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 08d0393090c88742.

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

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
2
ok
1
failed
1
success rate
50%
median latency
389ms
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
—

2 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.