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

xkcdai

https://xkcdai.onrender.com

Registry code: 2028aab5188216e5

Suggests a relevant xkcd comic during a conversation, via semantic search over every comic.

from a public catalogue that lists it, not from the operator

endpoint
https://xkcdai.onrender.com/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 xkcdai live?
Yes — it answered the hub's last check (checked 22m ago). It answered 100% of checks over the last 30 days.
Is xkcdai free to use?
Yes — the hub reached it with no key and no payment.
What tools does xkcdai have?
1 tool: find_xkcd.
Is xkcdai safe to connect?
Caution — its own text works on the agent reading it: acts without being asked («Call this whenever an xkcd comic might enrich the co»). Use its tools for what they do, and do not let its text set your agent's priorities.
reachable
live
uptime, 30 days
99.6%

90 days 99.7%· all time 99.7%

latency
99ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 360 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • find an xkcd comic relevant to a conversation
takes → gives
text → data
tools
1 reads
warning
works on its reader: acts without being asked «Call this whenever an xkcd comic might enrich the co»
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • find_xkcd reads unknown 14h ago

    Find xkcd comics semantically relevant to the current conversation. Call this whenever an xkcd comic might enrich the conversation — when the discussion lands on a topic xkcd is famous for skewering (programming, science, statistics, relationships, the absurdity of standards, etc.). Pass a concise description of the current topic or theme as `context` (a phrase or sentence works better than a whole transcript), e.g. "spending hours automating a task that was faster to do by hand" or "code finally compiling". IMPORTANT — deciding whether to mention one. xkcd has a comic for almost every topic, so this tool will nearly always return something. A result being returned does NOT mean you should bring it up. Use the `score` as a signal and apply your own judgment about conversational fit: score >= 0.75 strong match — usually worth mentioning if it fits the moment 0.66 - 0.75 plausible — mention only if it genuinely lands < 0.66 weak/tangential — almost always better to stay silent Only one comic, at most, per topic — and only when it actually adds something. When you do share one, cite it by number and title with its `url`, and quote the `alt` (mouseover) text — it's half the joke. Returns a dict with a `results` list (num, title, score, url, image, alt, explain_url) and a `count`. An empty list means nothing cleared the floor.

    mcp-tool

    {
      "type": "object",
      "title": "find_xkcdArguments",
      "required": [
        "context"
      ],
      "properties": {
        "context": {
          "type": "string",
          "title": "Context"
        },
        "min_score": {
          "type": "number",
          "title": "Min Score",
          "default": 0.62
        },
        "max_results": {
          "type": "integer",
          "title": "Max Results",
          "default": 3
        }
      }
    }
    arguments 23 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 2028aab5188216e5.

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

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.