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

wave-docs

https://docs.wave.online

Registry code: f874cba2909f95e2

api record

You are connected to the WAVE documentation MCP server. It serves the official docs corpus (guides, concepts, and reference for building on WAVE: media infrastructure for the agentic internet, called by people and by agents). Use docs_list to see every page with its summary, docs_read to read one page's markdown, or docs_search to find pages by keyword. The product ACTIONS live on the gateway MCP server at https://api.wave.online/mcp; this server is the learn surface.

endpoint
https://docs.wave.online/mcp
door code
19114b2f2e19d57f
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 wave-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is wave-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does wave-docs have?
3 tools: docs_read, docs_list, docs_search.
Is wave-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
99.2%

90 days 99.1%· all time 98.9%

latency
213ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 889 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search media infrastructure documentation
  • read a documentation page
  • list documentation pages
takes → gives
text → text
tools
3 reads
_ 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 3 tools
2 open 1 never probed 2 of 3 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.

  • docs_list reads open 10h ago

    List every WAVE documentation page with its title, category, and one-line summary.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • docs_search reads open 10h ago

    Search the documentation corpus by keyword; returns the matching pages with scored excerpts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search terms"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • docs_read reads unknown 10h ago

    Read one documentation page's full markdown by slug (e.g. quickstart, transports, billing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The page slug from docs_list"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 f874cba2909f95e2.

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

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.

_ also on wave.online 6 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.