Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
A

asherengos/verify-atom

Independent directory — not the official site. Details below come from the project's public repository.

The production backend for the verification atom: "check this one thing

Before you install: command ownership unverified - shown for reference only · license MIT

First step (reference only, ownership unverified): Install: uvx verify-atom-mcp (published on PyPI as verify-atom-mcp)

updated 2026-09-26
View on GitHub ↗Direct link · no redirect page

We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →

Star count
0 ★ · asherengos/verify-atom · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository asherengos/verify-atom;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# Verification Service ("the atom") — v1 backend

Excerpted from the repository README (abridged)

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:
cost_usd on every packet is an operator-configured estimate, not a
metered cloud bill ("cost_basis": "estimate"). Recalibrate before pricing.
Payments are disabled. There is no payment provider integration in v1,
and the service refuses to start if payments.enabled is true without one.
This service makes no revenue claims. Quoted prices are quotes; nothing
is charged, because nothing can be charged yet.
## 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)
| File | Role |
| app.py | Flask app: routes, SSRF-guarded HTTP observation, packet assembly |
| signing.py | Ed25519 key management + sign/verify (crypto core vendored from the Asher AI Studios Work Kernel, 2026-09-25; pure Python, RFC 8032, zero deps) |
| costs.py / cost_model.yaml | Per-verification usage measurement × operator-configured rates |
| ledger.py | Append-only JSONL ledger (data/ledger.jsonl): the board's source of truth and the honest loop's input |
| mini_yaml.py | Strict subset YAML reader (keeps deps to flask + waitress; not a general parser) |
| config.yaml | Service config: port, data dir, price, guardrails, payments switch |
| tests/test_service.py | Hermetic pytest suite (local stub server; no external network) |
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
bash
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):
bash
.venv/bin/python -m flask --app app:create_app run -p 5057
## API reference
### POST /verify — perform a verification
bash
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.
json
"id": "VRF-20260926-3f9a2c1d",
"type": "http_observation",
"verdict": "CONFIRMED",
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/asherengos-verify-atom/)
Source
awesome · https://github.com/asherengos/verify-atom
Browse by field
MCP servers
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index