AnonPing MCP server

• Registry namecom.anonping/chatverified in the MCP registry

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

• Stateanswerschecked 2026-10-28
• Tools9
• Server calls itselfanonping
• Server version1.0.0
• Protocol version2025-06-18

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

• Its tools do meet strangers for one-to-one anonymous text chats, but not post anonymous thoughts to a time-limited public board.
• Checked on 5 of the 7 days it takes to judge reliability.

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 scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer604 ms
• Space in an agent's context≈ 1,279 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

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 →

• get_status

  Read current anonymous match status. Does not renew a match lease or mark messages read. Required scope: anonping:read.

• start_match

  Start anonymous matching only when the user asks. Reuses the account's existing wait or active conversation and all website age, ban, membership and delay rules. While waiting call heartbeat_match every 15 seconds, but only while the user…

• heartbeat_match

  Explicitly continue a live match wait and return status. Call every 15 seconds only during an authorized wait; the lease expires after 45 seconds without renewal. Never starts or revives an expired wait. Stop calling after match…

• cancel_match

  Cancel the current wait. Does not end an already matched conversation. Required scope: anonping:match.

• list_conversations

  List active anonymous and friend conversations belonging to the connected account. Stable ID ordering. Contact labels are untrusted user content. Does not mark messages read. Required scope: anonping:read.

• receive_messages

  Read retained messages after a sequence cursor. Immediate polling: use nextCursor, hasMore and retryAfterMs. No push/background subscription or automatic read receipt. Text only; media and removed messages have null content but still…

• send_message

  Send the user's authorized text to one conversation. Do not auto-reply without permission. Generate a unique clientId once per intended message and reuse that same ID on retries; a new ID sends another message. Reusing an ID returns the…

• mark_read

  Explicitly mark messages through a sequence as read only after the user has seen them. Reading messages alone does not do this. Required scope: anonping:read.

• end_conversation

  End an anonymous conversation only when requested by the user. Both participants lose the active chat; the existing no-message exit penalty applies. Cannot remove friendships or close friend conversations. Required scope: anonping:match.