Skip to content
MCPSTAMP
MCP server report

Pondchat MCP server

com.pondchat/pondchat

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 83 of 100 (grade B), higher than 29.9% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
83B
Sign-in
OAuth
Tools listed
11
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC) and PKCE S256 advertised.
ChatGPT app directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC), issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT) and PKCE S256 advertised.
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields and PKCE S256 advertised.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

6 checks to fix

  1. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured https://pondchat.com/.well-known/oauth-authorization-server lacks response_types_supported:["code"]

    Add response_types_supported:["code"] to the authorization server metadata.

  2. Fails

    PKCE S256 advertised

    auth_pkce

    Blocks Claude, ChatGPT and Gemini.

    Measured code_challenge_methods_supported: []

    Support PKCE and advertise "code_challenge_methods_supported": ["S256"] (MCP clients refuse to proceed without it).

  3. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured https://pondchat.com/.well-known/oauth-authorization-server (first URL Gemini tries) lacks response_types_supported:["code"]

    Make https://pondchat.com/.well-known/oauth-authorization-server answer HTTP 200 with the authorization server metadata (authorization_endpoint, token_endpoint, response_types_supported ["code"], registration_endpoint). Gemini tries https:/

  4. Fails

    issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT)

    auth_chatgpt_metadata

    Blocks ChatGPT.

    Measured token_endpoint_auth_methods_supported missing

    Use the exact metadata "issuer" string in the protected resource metadata authorization_servers list (no trailing-slash or case differences), and list token_endpoint_auth_methods_supported (for example ["none"] for public clients) in the au

  5. Warning

    Client registration (DCR or Client ID Metadata Documents)

    auth_registration

    Measured No registration_endpoint and no client_id_metadata_document_supported

    Add a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.

  6. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: []

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

20 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Pondchat

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fpondchat.com%2Fapi%2Fmcp)](https://www.mcpstamp.com/r/com-pondchat-pondchat/)

HTML

<a href="https://www.mcpstamp.com/r/com-pondchat-pondchat/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fpondchat.com%2Fapi%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Ephemeral P2P WebRTC video rooms - create a pond, share the link, talk.
Registry name
com.pondchat/pondchat
Remote URL
https://pondchat.com/api/mcp
Version
1.0.0
Source
github.com/ivanaka/pondchat
Website
pondchat.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026