Webring MCP server

• Registry nameonline.webring/ringverified in the MCP registry

The registry name sits under webring.online. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools9
• Server calls itselfwebring-online
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 65 ms.

• Its tools do none of the product's use cases we checked: Publish an agent-ready website that other agents can traverse; Check an agentic.com score before paying to join.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score66 of 100answers 100 · does the job 0 · definitions 72 · context 100 · connects 100
• What an agent can do with it0 of 2 use cases
• Answered100% of days8 of 8 daily checks
• Median first answer181 ms
• Space in an agent's context≈ 542 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsC · 72 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 9
• Not saying whether it only reads or can destroy: 9 of 9

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• ring_list

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

• ring_next

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

• ring_prev

  The previous member around the ring (wraps).

• ring_random

  A random ring member.

• ring_member

  One member by slug, with leaderboard rank.

• ring_leaderboard

  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.

• ring_categories

  Categories in use, with member counts.

• ring_join_info

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

• ring_bid_info

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