MCP.Market

verify-atom MCP server

by asherengos·io.github.asherengos/verify-atom·v0.1.0
No reviews yet

Signed proof of web observations for AI agents: Ed25519 proof packets for any URL.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed verify-atom yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

verify-atom tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How verify-atom compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers

Install verify-atom in Claude Code, Cursor or VS Code

claude mcp add verify-atom -- uvx verify-atom-mcp
Add to Cursor

What the publisher says

From the verify-atom repository's README, as published. We do not edit it. Read it on GitHub

Verification Service ("the atom") — v1 backend

The production backend for the verification atom: "check this one thing for me, and prove you did." A client POSTs one question (http_observation of a URL); the service performs a real observation and returns a signed proof packet with transparent cost accounting. Every verification is appended to a public, permanent ledger — the board.

Honesty, up front:

metered cloud bill ("cost_basis": "estimate"). Recalibrate before pricing.

  • costusd on every packet is an operator-configured estimate**, not a

and the service refuses to start if payments.enabled is true without one.

  • Payments are disabled. There is no payment provider integration in v1,

is charged, because nothing can be charged yet.

  • This service makes no revenue claims. Quoted prices are quotes; nothing

Architecture

MCP server (mcp/)

This repo also ships a Model Context Protocol server that exposes the verification atom as an MCP tool, so MCP-compatible agents can request signed proof packets directly.

  • Install: uvx verify-atom-mcp (published on PyPI as verify-atom-mcp)
  • Listed in the official MCP registry as io.github.asherengos/verify-atom
  • Transport: stdio · Tool: verify — performs an HTTP observation of a URL and returns the Ed25519-signed proof packet
  • Source: mcp/mcp_server.py (zero dependencies; mcp/README.md has the details)

A verification flows: POST /verify → SSRF guard → real socket-level HTTP fetch (single DNS resolution; the checked address is the connected address; redirects never followed) → observation + evidence → cost accounting → Ed25519 signature over canonical JSON → append to ledger → proof packet.

Quick start

cd ~/workspace/verify-service
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt   # flask + waitress only; free
.venv/bin/python app.py                     # serves on 127.0.0.1:5057 via waitress

First run generates an Ed25519 keypair under data/keys/ (0600). data/ is gitignored: ledger, keys, and runtime state never enter the repo.

Development (Flask built-in server, do not use in production):

.venv/bin/python -m flask --app app:create_app run -p 5057

API reference

POST /verify — perform a verification

curl -s -X POST http://127.0.0.1:5057/verify \
  -H 'Content-Type: application/json' \
  -d '{"type":"http_observation","url":"https://example.com"}' | python3 -m json.tool

Response: a signed proof packet.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

verify-atom: common questions

Is verify-atom MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the verify-atom safety report
How do I install verify-atom?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does verify-atom need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is verify-atom maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v0.1.0.
What can I use instead of verify-atom?
Servers from other publishers that do the same job: Reticle MCP server.

Alternatives to verify-atom

Same job from other publishers: the closest match first, then the best rated.

  • Reticle
    Verify a running web app from the inside over MCP: look, act, observe, assert. No screenshots.
    B