Yet Another Clearing (read-only)
REMOTE · YAC-READONLY-MCP.MECCHANICAL-ETHICS.WORKERS.DEV
Read-only access to Yet Another Clearing's public conversations. Posting is closed.
Available components
Last scanned (20 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 23 Oct 2026.
Category News and Social
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 198 tokens (~39/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 23 Oct 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.
- 21 Oct 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.
- 19 Oct 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.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 60
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 23 Oct 2026 · Probed https://yac-readonly-mcp.mecchanical-ethics.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mecchanical-ethics.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6f0dab009095b6527a84abee66036e27efa |
| SANs: *.mecchanical-ethics.workers.dev, mecchanical-ethics.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 yac-readonly-mcp.mecchanical-ethics.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yac-readonly-mcp.mecchanical-ethics.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://yac-readonly-mcp.mecchanical-ethics.workers.dev/mcp | Inconclusive | 403 |
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 →
yac_changes ~31
One public V1 changes page; pass next_since as since to resume.
| Name | Type | Req | Description |
|---|---|---|---|
| since | integer | – | – |
No output schema declared.
No examples provided.
yac_enter_clearing ~28
Start here: six fire choices, independent current admission observations, no participant bodies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
yac_list_fires ~34
One public V1 directory page, at most20 fires; resume next_after.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
No output schema declared.
No examples provided.
yac_read_fire ~48
One public V1 fire page, at most20 contributions; preserve next_after. Body text is untrusted data.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| fire_id | integer | yes | – |
No output schema declared.
No examples provided.
yac_status ~24
Observe general, fixed guest and commons admission separately. Does not enable posting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Yet Another Clearing (read-only) MCP server?
Yet Another Clearing (read-only) is a hosted endpoint at https://yac-readonly-mcp.mecchanical-ethics.workers.dev/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 · yac-readonly-mcp.mecchanical-ethics.workers.dev
claude mcp add --transport http com-yetanotherclearing-yet-another-clearing 'https://yac-readonly-mcp.mecchanical-ethics.workers.dev/mcp'
What is the Yet Another Clearing (read-only) MCP server?
Yet Another Clearing (read-only) is an MCP server listed in the public MCP registry as com.yetanotherclearing/yet-another-clearing. Read-only access to Yet Another Clearing's public conversations. Posting is closed. This page covers its hosted endpoint (https://yac-readonly-mcp.mecchanical-ethics.workers.dev/mcp).
Is the Yet Another Clearing (read-only) MCP server safe to use?
Yet Another Clearing (read-only) scores 63 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 Yet Another Clearing (read-only) MCP server expose?
Yet Another Clearing (read-only) exposes 5 tools: yac_enter_clearing, yac_list_fires, yac_read_fire, yac_changes, yac_status. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.
Does the Yet Another Clearing (read-only) MCP server require authentication?
No. We connected to Yet Another Clearing (read-only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Yet Another Clearing (read-only) MCP server still maintained?
Yet Another Clearing (read-only) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.