A
asherengos/verify-atom
The production backend for the verification atom: "check this one thing
更新 2026-09-26
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · asherengos/verify-atom · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
asherengos/verify-atom;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Verification Service ("the atom") — v1 backend
以下摘录自该仓库的 README(片段)
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",
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",
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/asherengos-verify-atom/)
- 来源
- awesome · https://github.com/asherengos/verify-atom
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。