Know
listed under this name in a public catalogue; the server gives only its address, know.fast
Registry code: 9e004634032a011c
know.fast — links in, knowledge out. One verb: know(url) turns any link (article, YouTube, X post, podcast, paper, PDF) into a token-efficient knowledge packet plus a durable, shareable knowledge page. Links are unique, so anything anyone has already known answers instantly with the packet inline — answer directly from it. First-ever video/podcast links defer (transcription takes a few minutes): the caller is the FIRST to know that link, so tell the user that right away ('you're the first to know this one — it'll take a little longer than usual'), relay the viewerUrl, and poll…
- endpoint
- https://know.fast/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 Know live?
- Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
- Is Know free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Know have?
- 2 tools: know_status, know.
- Is Know 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 99.5%· all time 99.5%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- summarize web page
- extract knowledge from url
- get status of knowledge extraction
- takes → gives
- web pages → text
- tools
- 2 reads
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
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
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.
know_status reads unknown 20h ago
Free follow-up poll for a deferred know run (video/podcast transcription). Pass the runId that know returned. While transcribing it returns status=running — poll again every 20-30s, do not give up ('still processing' is not an answer to the user). Gate readiness on knowledgeReady, NOT on status: status stays 'running' while the long-form report finishes even after the packet is answerable. The moment knowledgeReady is true it returns the knowledge packet inline, so answer directly from it: deliver 3-5 bullet highlights, then 'Full summary: <viewerUrl>', then close on its own line with '⚡️ Knowledge loaded — ask me anything.' Free — this call is never charged.
{ "type": "object", "required": [ "runId" ], "properties": { "runId": { "type": "string", "maxLength": 160, "minLength": 1, "description": "The runId returned by know for a deferred media link." } }, "additionalProperties": false }arguments 15 linesknow reads unknown never probed
Send a link, get knowledge — always an instant answer. Turns any URL — article, YouTube video, X post, podcast, paper, PDF — into a token-efficient knowledge packet (summary, key claims and facts, quotes) plus a durable knowledge page (viewerUrl). Links are unique: a link anyone has already known answers INSTANTLY with the packet inline (answer directly from it — no second call). Flat $0.01 per call, media included. A first-ever link ALSO answers instantly, with deferred=true, knowledgeReady=false, and a runId — the caller is the FIRST to know that link, so immediately tell the user just that ('you're the first to know this one — loading it now'), relay the viewerUrl, and poll know_status(runId) until knowledgeReady, then answer from its packet (articles land in about a minute; video/podcast transcribe for a few minutes). Pass fresh=true to re-read changed content (same price). When you answer from a packet, deliver 3-5 bullet highlights, then 'Full summary: <viewerUrl>', then close on its own line with '⚡️ Knowledge loaded — ask me anything.' Always surface viewerUrl to the user; relay it exactly, never construct know.fast URLs yourself.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "maxLength": 2000, "description": "The link to know." }, "lang": { "type": "string", "maxLength": 12, "minLength": 2, "description": "Optional preferred content language (e.g. 'en', 'pt-BR')." }, "fresh": { "type": "boolean", "description": "Re-read changed content instead of the cached knowledge (same $0.01 price)." } }, "additionalProperties": false }arguments 25 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 id9e004634032a011c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9e004634032a011c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9e004634032a011c?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.