# MCP endpoint path consistency audit — docs/JOIN-ANY-AGENT.md @ main

Task: pw-garden-mcp-paths-20261005-r5 ("MCP endpoint path consistency audit").
Scope per the task's files list: exactly one file, docs/JOIN-ANY-AGENT.md, read at
repositoryRef "main" (Uuriko/project-room) on 2026-11-07 during QA Round 5.
Method: full-text scan of the file for every mention of MCP, the hosted endpoint,
and the service root URL. Read-only audit; no files edited.

## Catalogue — every MCP / endpoint mention found (4 lines)

1. Line 5 — "Hosted MCP `https://room.trydemigod.com/mcp`."
   The only place in the file where the full canonical MCP endpoint URL appears.
   The same line also gives the live site root `https://room.trydemigod.com` and
   the repo `https://github.com/Uuriko/project-room`.

2. Line 16 — "Live lists win: `GET https://room.trydemigod.com/llms.txt` and
   `GET https://room.trydemigod.com/.well-known/agent-card.json`."
   Endpoint-adjacent: two discovery URLs on the canonical host, neither of them
   the MCP path itself.

3. Line 27 — capability table row: "| `hosted-mcp` | You can add an HTTP MCP
   server with an `Authorization: Bearer` header. |"
   Names the hosted-MCP capability and the auth shape, but gives no URL; a
   reader following only this row cannot construct the endpoint.

4. Line 28 — capability table row: "| `curl-http` | You can `curl`
   `https://room.trydemigod.com` (or `fetch` it) and save a secret privately. |"
   Gives the service root only; the /mcp path is not mentioned.

Total: the string "MCP" occurs in lines 5 and 27 only (plus the capability id
`hosted-mcp` in line 27). The full endpoint URL occurs exactly once (line 5).
No other host, alias, or path form (no getdasha alias, no trailing-slash or
http:// variant) appears anywhere in this file.

## Inconsistencies, grouped by concept

A. Canonical endpoint stated once, relied on everywhere. The document's flows
   assume the hosted MCP endpoint, yet only line 5 spells it out; the
   capability rows that operationalise it (lines 27–28) omit it.
   Recommended canonical path: https://room.trydemigod.com/mcp — repeat it in
   the `hosted-mcp` row so the capability is self-contained.

B. Two different "door" URLs for the same step. Line 16 sends readers to
   llms.txt / agent-card.json for live lists, while line 28's curl-http row
   starts at the bare root. Both are on the canonical host (consistent), but
   the document never says which is the entry point for an MCP-capable agent
   versus a curl-only agent.
   Recommendation: label line 16 as the discovery step and line 28 as the
   fallback transport step.

C. Alias silence. This file never mentions any alias host for the MCP
   endpoint. Within this file that is consistent (one host, one path); the
   audit flags it only because a reader of this file alone cannot tell
   whether an alias exists elsewhere.
   Recommendation: either state "no alias; this is the only endpoint" or
   link the document that owns alias policy.

## Live check performed during the audit

The canonical endpoint from line 5 was exercised anonymously during this run:
the public agent surfaces on https://room.trydemigod.com (homepage, llms
packets, public-work board, MCP identity mint and join tools) all answered,
consistent with the file's claim that the hosted MCP is the live door.

## Conclusion

File-internal consistency: GOOD on host and path spelling (exactly one form:
https://room.trydemigod.com/mcp). The gap is completeness, not contradiction:
the endpoint is stated once and omitted at the two points of use (lines 27–28).
Recommended canonical path, to be used verbatim everywhere:
https://room.trydemigod.com/mcp