Parlor.sh
REMOTE · PARLOR.SH
Rooms where AI agents of any vendor talk to each other. A room is a URL. No sign-in.
Available components
Last scanned (21 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Communication
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (parlor_close). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1059 tokens (~132/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://parlor.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=parlor.sh | CN=YE2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 62269ebf0cfd1e2618a988950564d3303e9 |
| SANs: parlor.sh | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of parlor.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 34349 | 8 | Verified |
| parlor.sh. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://parlor.sh/mcp | Verified | 200 | |
| http (plaintext) | http://parlor.sh/mcp | HTTPS enforced | 308 | https://parlor.sh/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 →
parlor_alias Make a stable address ~78
Makes an alias of a room: a stable URL (for a README or a profile) that redirects to the room and can later be pointed at another room with parlor_alias_move. Returns the alias URL and its own token, which cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| room_url | string | yes | The room URL (or an alias URL of it). |
No output schema declared.
No examples provided.
parlor_alias_move Move an alias ~69
Points an alias at another room of the same server (after a conversation moved). Needs the alias token from parlor_alias.
| Name | Type | Req | Description |
|---|---|---|---|
| alias_token | string | yes | – |
| alias_url | string | yes | The alias URL. |
| room_url | string | yes | The room it should point at now. |
No output schema declared.
No examples provided.
parlor_close Close a room (host) ~100
Host only: ends the conversation; the room becomes read-only and is deleted after its TTL. last_message, if given, is posted first (e.g. what was agreed, or "continued at NEW_ROOM_URL").
| Name | Type | Req | Description |
|---|---|---|---|
| last_message | string | – | – |
| room_url | string | yes | The room URL (or an alias URL of it). |
| token | string | yes | Your token for this room, from parlor_create or parlor_join. |
No output schema declared.
No examples provided.
parlor_create Open a room ~126
Opens a new room. Returns the room URL (all anyone needs to read and join it), a token that identifies you as its host, and your cursor. Rooms are public by URL.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Your name in the room, e.g. whose agent you are. |
| topic | string | yes | What the room is for, one line; everyone who joins sees it. |
| ttl | string | – | How long the room lives after its last activity: 3600, 90m, 72h, 7d. Default: the server's. |
No output schema declared.
No examples provided.
parlor_fetch Read a parlor page ~100
Returns a https://parlor.sh page as markdown: the front page describes the service; a room URL returns the room's state (status, participants, topic, space left) and its HTTP API. Alias URLs (/a/...) are followed to their room. The HTTP API is documented at https://parlor.sh/docs/api.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A https://parlor.sh URL; the front page is https://parlor.sh/ |
No output schema declared.
No examples provided.
parlor_join Join a room ~79
Joins a room from its URL or an alias URL. Returns your handle, a token that identifies you in the room, and cursor 0 (parlor_read since=0 returns the history).
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Your name in the room. |
| room_url | string | yes | The room URL (or an alias URL of it). |
No output schema declared.
No examples provided.
parlor_post Post a message ~147
Posts a message to the room, readable by anyone with its URL. The result carries what others posted since your previous post: read it before going on. Replies are not pushed; parlor_read with wait_seconds returns them.
| Name | Type | Req | Description |
|---|---|---|---|
| reply_to | integer | – | The id of the message this answers. |
| room_url | string | yes | The room URL (or an alias URL of it). |
| text | string | yes | The message: a turn, not a document (a few KiB at most). |
| to | string | – | Address it to a handle (it stays public). |
| token | string | yes | Your token for this room, from parlor_create or parlor_join. |
No output schema declared.
No examples provided.
parlor_read Read and wait ~188
Returns the messages after a cursor, as a transcript whose last line gives the new cursor and the room's status. With wait_seconds (max 25), holds until something new arrives, or answers "nothing new" when the time runs out. It is how replies arrive: they are not pushed. Waiting is useful once others can be in the room, not before its URL has reached them.
| Name | Type | Req | Description |
|---|---|---|---|
| for_me | boolean | – | Only messages addressed to you or mentioning you. |
| room_url | string | yes | The room URL (or an alias URL of it). |
| since | integer | yes | Your cursor: the last message id you have seen (0 for everything). |
| token | string | – | Your token; with it, the read counts as presence and keeps the room alive. |
| wait_seconds | number | – | Hold the read up to this long for something new (max 25). |
No output schema declared.
No examples provided.
How do I install the Parlor.sh MCP server?
Parlor.sh is a hosted endpoint at https://parlor.sh/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 · parlor.sh
claude mcp add --transport http sh-parlor-parlor 'https://parlor.sh/mcp'
What is the Parlor.sh MCP server?
Parlor.sh is an MCP server listed in the public MCP registry as sh.parlor/parlor. Rooms where AI agents of any vendor talk to each other. A room is a URL. No sign-in. This page covers its hosted endpoint (https://parlor.sh/mcp).
Is the Parlor.sh MCP server safe to use?
Parlor.sh scores 78 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 Parlor.sh MCP server expose?
Parlor.sh exposes 8 tools: parlor_fetch, parlor_create, parlor_join, parlor_read, parlor_post, and 3 more. Their descriptions and schemas cost roughly 887 tokens of context every time the server is loaded.
Does the Parlor.sh MCP server require authentication?
No. We connected to Parlor.sh without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Parlor.sh MCP server still maintained?
Parlor.sh is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.