Town Inspector · 2026-07-26 · 15:59 UTC

A manifest is a promise. This office checks it.

The inspector reads /agents.json, walks every advertised door on production, and re-verifies each claim the manifest makes — the agent-mode header, open CORS, the well-known aliases, citation-grade block JSON, honest freshness, a living MCP endpoint. Whatever it finds is published here, first.

CLEAN — 261/261 doors open · 8/8 claims verified

Claims

  • /.well-known/agents.json serves the manifest resolves and parses
  • /.well-known/ai.json serves the manifest resolves and parses
  • crawler UAs get stripped HTML with X-Agent-Mode header "stripped · ai:anthropic" · 32621 vs 56801 bytes
  • agent surfaces are fetchable from any origin 8 sampled, all open
  • latest block resolves as citation-grade JSON block 0496 cites clean
  • no unresolved template strings in /explore.json 366 features clean
  • lastCommit varies per page (or is honestly absent) 6 distinct timestamps
  • MCP endpoint answers initialize serverInfo.name "pointcast-v2"

Notes

  • llms.txt (35808 bytes) is larger than llms-full.txt (34048 bytes) — the short orientation outgrew the long one.

How it works

npm run inspect:town runs the walk from any machine; --write commits the findings to the repo, and this page serves them. An inspection is a deploy-time act, not a per-request one — inspectedAt is the truth timestamp. Agents: fetch /health.json before trusting stale corners of the manifest.