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

webring-online

https://webring.online

Registry code: 36c2702ea961dc19

api record

Traversable webring directory for the agentic web. Free tools traverse and read the ring; joining and bidding are paid over MPP via the REST API (ring_join_info / ring_bid_info explain the flow).

endpoint
https://webring.online/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 webring-online live?
Yes — it answered the hub's last check (checked 36m ago). It answered 100% of checks over the last 30 days.
Is webring-online free to use?
Yes — the hub reached it with no key and no payment.
What tools does webring-online have?
9 tools: ring_join_info, ring_next, ring_prev, ring_random, ring_member, ring_leaderboard, ring_categories, ring_bid_info, ….
Is webring-online 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.5%

90 days 99.4%· all time 99.4%

latency
130ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 345 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
search & web
used for
  • browse webring members
  • get next site in webring
  • see webring leaderboard
takes → gives
text → data
tools
9 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 9 tools
1 open 8 never probed 1 of 9 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.

  • ring_list reads open 7h ago

    Webring members in ring order. Optional kind/category filters and limit/offset pagination.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "kind": {
      "enum": [
        "agent",
        "mcp",
        "website"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "category": {
      "type": "string"
    }
  }
}
    arguments 25 lines
  • ring_join_info reads unknown never probed

    How to join the ring: fee, validation requirements, and the MPP (HTTP 402) payment flow.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • ring_next reads unknown never probed

    The next member around the ring from a slug, URL, or hostname (wraps). Omit from to enter at the start.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "from": {
      "type": "string"
    },
    "kind": {
      "enum": [
        "agent",
        "mcp",
        "website"
      ],
      "type": "string"
    },
    "category": {
      "type": "string"
    }
  }
}
    arguments 19 lines
  • ring_prev reads unknown never probed

    The previous member around the ring (wraps).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "from": {
      "type": "string"
    },
    "kind": {
      "enum": [
        "agent",
        "mcp",
        "website"
      ],
      "type": "string"
    },
    "category": {
      "type": "string"
    }
  }
}
    arguments 19 lines
  • ring_random reads unknown never probed

    A random ring member.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "kind": {
      "enum": [
        "agent",
        "mcp",
        "website"
      ],
      "type": "string"
    },
    "category": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • ring_member reads unknown never probed

    One member by slug, with leaderboard rank.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • ring_leaderboard reads unknown never probed

    Members ranked by total paid (join fee plus anything paid on top; totals never shrink); earlier join wins ties; #1 holds the homepage spot. to_take_first_usd is the single payment that takes #1. Optional limit/offset.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    }
  }
}
    arguments 14 lines
  • ring_categories reads unknown never probed

    Categories in use, with member counts.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • ring_bid_info reads unknown never probed

    How to pay a member up the leaderboard: minimum, ranking rules, and the MPP payment flow.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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 36c2702ea961dc19.

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

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.