_ registry / mcp streamable-http · checked 1h 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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
234ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ 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 open 1h 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_next 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 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 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_join_info 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_member 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 unknown never probed

    Members ranked by standing bid totals (cumulative, but decaying when quiet; any new bid revives the full total); #1 holds the homepage spot. to_take_first_usd is the single bid 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 unknown never probed

    Categories in use, with member counts.

    mcp-tool

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

    How to bid a member up the leaderboard: minimum, auction 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.

_ 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)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.