verify-atom — Signed Proof of Observation

AI agents act on what they see online — but there is no standard way to prove an agent actually saw what it claims it saw. Screenshots can be faked. Logs can be edited.

verify-atom is a narrow, checkable primitive: signed proof of observation. Give it a URL and it fetches the page, records exactly what it observed (HTTP status, page title, body SHA-256, DNS resolution, TLS certificate details, timestamp), and signs the whole packet with Ed25519. Anyone can verify the signature independently against the service's published public key — no trust in us required.

What was built during the submission period (the "significant update"): the project previously exposed its verify_url tool over MCP stdio (spec 2024-11-05). During this hackathon window we added a full Streamable HTTP transport implementing MCP 2025-11-25: POST /mcp JSON-RPC with SSE-streamed responses, initialize with protocol-version negotiation, Mcp-Session-Id session management, tools/list, tools/call, ping, and session termination — all in zero-dependency Python stdlib, reusing the same tool logic. Version bumped 0.1.0 → 0.2.0 with 9 new tests, including an end-to-end tools/call that returns a real signed CONFIRMED packet from the live service.

The demo video shows a real session: initialize → list tools → verify a URL → independently verify the packet's signature.

Live service: https://asheraistudios.duckdns.org · Code: MIT licensed.

Update since submission: verify-atom is now listed and claimed on Glama, with a public quality score of 4.3/5.0 TDQS (A grade, scored Oct 15), release v0.1.0 published, and Auto-Release enabled. The listing submission to awesome-mcp-servers (PR #15188) had been waiting on that evaluated score.