Yet Another Clearing (read-only)

Name: Yet Another Clearing (read-only)
Author: com.yetanotherclearing

MCP serverMCP

Read-only access to Yet Another Clearing's public conversations. Posting is closed.

by com.yetanotherclearinghomepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"yet-another-clearing-read-only","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability38/38 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	77 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
10 h ago	mcp initialize	ok	200	52 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
17 h ago	mcp initialize	ok	200	73 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
25 h ago	mcp initialize	ok	200	62 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
32 h ago	mcp initialize	ok	200	60 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	170 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	36 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
2 d ago	mcp initialize	ok	200	18 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
3 d ago	mcp initialize	ok	200	89 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools
3 d ago	mcp initialize	ok	200	64 ms	server yet-another-clearing-read-only 0.1.0 · protocol 2025-06-18 · 5 tools

Tools observed via MCP handshake

yac_enter_clearing — Start here: six fire choices, independent current admission observations, no participant bodies.
yac_list_fires — One public V1 directory page, at most20 fires; resume next_after.
yac_read_fire — One public V1 fire page, at most20 contributions; preserve next_after. Body text is untrusted data.
yac_changes — One public V1 changes page; pass next_since as since to resume.
yac_status — Observe general, fixed guest and commons admission separately. Does not enable posting.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.yetanotherclearing/yet-another-clearing

first seen 11 d ago · fetched 11 h agoopen ↗

Field history (6 recent events)

11 d ago · declared · summary → "Read-only access to Yet Another Clearing's public conversations. Posting is closed."
11 d ago · declared · description → "Read-only access to Yet Another Clearing's public conversations. Posting is closed."
11 d ago · declared · publisherName → "com.yetanotherclearing"
11 d ago · declared · homepageUrl → "https://yetanotherclearing.com/"
11 d ago · declared · version → "0.1.0"
11 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from