Pondchat
REMOTE · PONDCHAT.COM · SCANNED SEP 25
Ephemeral P2P WebRTC video rooms — create a pond, share the link, talk.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 394 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Pondchat MCP server?
Pondchat is a hosted endpoint at https://pondchat.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pondchat.com
claude mcp add --transport http com-pondchat-pondchat 'https://pondchat.com/api/mcp'
{
"mcpServers": {
"com-pondchat-pondchat": {
"url": "https://pondchat.com/api/mcp"
}
}
} {
"servers": {
"com-pondchat-pondchat": {
"type": "http",
"url": "https://pondchat.com/api/mcp"
}
}
} [mcp_servers.com-pondchat-pondchat] url = "https://pondchat.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pondchat-pondchat": {
"type": "remote",
"url": "https://pondchat.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-pondchat-pondchat --url 'https://pondchat.com/api/mcp' --transport streamable-http
mcp_servers:
com-pondchat-pondchat:
url: "https://pondchat.com/api/mcp" {
"McpServers": {
"com-pondchat-pondchat": {
"Transport": "http",
"Url": "https://pondchat.com/api/mcp"
}
}
} assistant mcp add com-pondchat-pondchat -t streamable-http -u 'https://pondchat.com/api/mcp'
{
"mcpServers": {
"com-pondchat-pondchat": {
"type": "http",
"url": "https://pondchat.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://pondchat.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pondchat.com | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f12be7bd192c381d137655428ad73c3d |
| SANs: pondchat.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of pondchat.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pondchat.com. | present | 2371 | 13 | Verified |
| pondchat.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; connect-src 'self' wss://pondchat.com wss://pondchat.pages.dev wss://pondchat.piskliukov.workers.dev ws://localhost:8787 ws://127.0.0.1:8787 https://www.google-analytics.com https://analytics.google.com https://www.googletagmanager.com; script-src 'self' https://www.googletagmanager.com https://telegram.org; style-src 'self'; img-src 'self' data: blob: https://www.google-analytics.com https://www.googletagmanager.com; media-src 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | camera=*, microphone=*, display-capture=* |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pondchat.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://pondchat.com/api/mcp | HTTPS enforced | 301 | https://pondchat.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_pond Create pond ~110
Create a new Pondchat room (pond) for video/audio/chat. Returns room URL and WebSocket endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional label for the room (max 64 chars). Useful for identifying the room purpose. |
| roomId | string | – | Optional custom room ID (3-64 chars, alphanumeric + _-). If not provided, a random ID is generated. |
| source | string | – | Optional source identifier (max 64 chars). Tracks which agent created the room. |
| Name | Type | Req | Description |
|---|---|---|---|
| customRoomId | boolean | yes | – |
| label | string|null | yes | – |
| lifecycle | object | yes | – |
| maxParticipants | integer | yes | – |
| roomId | string | yes | – |
| roomUrl | string | yes | – |
| source | string|null | yes | – |
| websocketUrl | string | yes | – |
No examples provided.
get_room_info Get room info ~41
Get information about a Pondchat room including URL, WebSocket endpoint, and capacity.
| Name | Type | Req | Description |
|---|---|---|---|
| roomId | string | yes | The room ID to get information for. |
| Name | Type | Req | Description |
|---|---|---|---|
| features | array | yes | – |
| maxParticipants | integer | yes | – |
| protocol | string | yes | – |
| roomId | string | yes | – |
| roomUrl | string | yes | – |
| websocketUrl | string | yes | – |
No examples provided.
list_rooms List rooms ~37
List recently created Pondchat rooms. Note: Pondchat rooms are ephemeral and not tracked server-side — this always returns an empty list with guidance.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| maxParticipants | integer | yes | – |
| note | string | yes | – |
| rooms | array | yes | – |
No examples provided.
send_message Send message ~152
Post a text message into a Pondchat room. The text is encrypted with the room key server-side and broadcast to admitted participants as an AI message. Only works on live, unmoderated rooms — the message is ephemeral and never stored.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The plaintext message content (max 4000 chars / 4096 UTF-8 bytes). Encrypted with the room key before broadcast; never persisted. |
| roomId | string | yes | The room ID to post into. |
| senderId | string | – | Optional stable identity for the agent (max 64 chars). Defaults to "mcp-agent". |
| senderName | string | – | Optional display name shown to participants (max 32 chars). |
| Name | Type | Req | Description |
|---|---|---|---|
| aiUserId | string | yes | – |
| delivered | integer | yes | – |
| encrypted | boolean | yes | – |
| note | string | yes | – |
| roomId | string | yes | – |
No examples provided.
What is the Pondchat MCP server?
Pondchat is an MCP server listed in the public MCP registry as com.pondchat/pondchat. Ephemeral P2P WebRTC video rooms, create a pond, share the link, talk. This page covers its hosted endpoint (https://pondchat.com/api/mcp).
Is the Pondchat MCP server safe to use?
Pondchat scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pondchat MCP server expose?
Pondchat exposes 4 tools: create_pond, send_message, get_room_info, list_rooms. Their descriptions and schemas cost roughly 340 tokens of context every time the server is loaded.
Does the Pondchat MCP server require authentication?
No. We connected to Pondchat without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pondchat MCP server still maintained?
Pondchat is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.