webref
https://webref.johnaio281.workers.dev
Registry code: f1516a97ca7a4394
Call a tool with a JSON object of arguments. Tool calls are billed per call in USDC on Base (x402 v2); discovery (tools/list) is free. Prices are in each tool description.
- endpoint
- https://webref.johnaio281.workers.dev/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 webref live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is webref free to use?
- No — it charges per call, from 0.003 USDC, quoted in its own 402 answers.
- What tools does webref have?
- 7 tools: http_status, status_for_situation, http_method, retry_advice, mime_type, content_type_advice, list_mime_types.
- Is webref 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.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
http_method 0.003 USDC paid never probed
Describe an HTTP method: whether it is safe, whether it is idempotent, whether it carries a body, and what it is for. ($0.003 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "method" ], "properties": { "method": { "type": "string", "description": "e.g. GET, POST, PATCH" } } }arguments 13 linesretry_advice 0.005 USDC paid never probed
Decide how a client should react to a status code: retry with backoff, check the outcome before retrying, or do not retry. Includes a suggested backoff schedule. ($0.005 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "code" ], "properties": { "code": { "type": [ "number", "string" ] }, "idempotent": { "type": "boolean", "default": true, "description": "whether the request being handled is idempotent" } } }arguments 20 linesmime_type 0.003 USDC paid never probed
Look up a MIME type by full type or by file extension: the top-level type, what it is for, and the usual file extension. ($0.003 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "type": { "type": "string", "description": "full type, e.g. application/json" }, "extension": { "type": "string", "description": "extension, with or without the dot" } } }arguments 14 linescontent_type_advice 0.003 USDC paid never probed
Check whether a Content-Type header matches what an endpoint kind expects, and say what to send instead when it does not. ($0.003 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "contentType", "endpointKind" ], "properties": { "contentType": { "type": "string", "description": "the Content-Type header value" }, "endpointKind": { "enum": [ "json", "form", "multipart", "xml", "text", "binary" ], "type": "string", "description": "what the endpoint expects" } } }arguments 26 lineslist_mime_types 0.003 USDC paid 1h ago
List or search MIME types by top-level type or by keyword, for example image types or anything to do with calendars. ($0.003 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "default": 50 }, "query": { "type": "string" }, "topLevel": { "type": "string", "description": "application, text, image, audio, video, font, model, multipart, message, example" } } }arguments 17 lineshttp_status unknown 1h ago
Look up an HTTP status code: what it means, what the client must do, whether it is retryable, whether it is safe to replay, the defining RFC and the common causes. ($0.003 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "code" ], "properties": { "code": { "type": [ "number", "string" ], "description": "status code, e.g. 429" }, "detail": { "enum": [ "summary", "full", "decision" ], "type": "string", "default": "full", "description": "summary = name and class only; decision = what the client should do" } } }arguments 26 linesstatus_for_situation unknown 1h ago
Find the HTTP status code that matches a described situation, when the code is not known in advance — for example 'the caller is being rate limited' or 'upstream returned garbage'. ($0.005 per call)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "situation" ], "properties": { "situation": { "type": "string", "description": "free text describing what went wrong" } } }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf1516a97ca7a4394.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f1516a97ca7a4394/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f1516a97ca7a4394?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.