zerobeacon-1000-tool-collision-proof-commerce-router

MCP开发工具

提供方 DavidFox998

开发工具 未标注 API Key 社区 / 第三方 ClaudeCursorVS CodeCodex

由 DavidFox998 提供的 MCP 服务器,未标注。

一句话选型结论

按资料字段整理

zerobeacon-1000-tool-collision-proof-commerce-router 属于开发工具类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

ecommerce commerce mcp mcp server ai agents paypal stripe trust

支持客户端

适用场景

ecommercecommercemcp

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
zerobeacon-1000-tool-collision-proof-commerce-router当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方DavidFox998上游标注的维护方 DavidFox998
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

9.9 KB
来自项目仓库与上游目录的原文,未做删改

ZeroBeacon.ai — Collision-Anchored Commerce Router

1,003 MCP operations for agent commerce, legal sealing, and math research.
Live API: https://zerobeacon.ai
MCP endpoint: POST https://zerobeacon.ai/mcp — Streamable HTTP; negotiates protocol revisions 2024-11-05 through 2025-11-25.
Counts, reconciled: tools/list returns the 1,003 operations callable over MCP; /health reports tools: 1052, routers: 21 — the full catalogue, including the REST-only endpoint surface. Both figures are live-checkable.


What this is (and what it isn't)

ZeroBeacon has two distinct layers:

Layer What it does Collision claim
Commerce Router (tools 1–1000) Escrow, notary, delivery proof, wills, mesh treasury Collision-anchored — 9 controlled collisions at moat anchors P1/P2
Opera Numerorum (research lab) Arakelov, Riemann Hypothesis, BSD, Navier-Stokes, Yang-Mills, P vs NP math tools Probabilistic guarantees; not a proof system

The beacon is not collision-proof and does not claim to be.
It is collision-anchored: two known primes (P1 = 3000105001, P2 = 5303687339) are intentional fixed points that produce the canonical beacon value 1d2c7a5b. Everything else is probabilistic.

Every tool is registered at its own block-anchored address, /api/mf/{block}/{tool} (e.g. /api/mf/01/beacon). Tool names repeat across blocks by design; the address, not the name, is a tool's identity.
The addressing is generated from four primes — 11, 13, 17, 19 — and the constant 1419 = 3 × 11 × 43.
The anchoring method descends from the Eutheos programme, a Lean 4–verified witness family maintained in the separate eutheos-property repo. That verification covers the witness family, not this API.


The Trust Layer

ZeroBeacon's toolset gives agents tools to call. The trust layer
checks the work those calls produce before anyone relies on it.

In plain terms: an agent submits a piece of work and the claims
that come with it. The trust layer re-measures the claims instead
of believing them, checks them live against the real system, and
then either certifies the result or refuses it and names the
check that failed. Every outcome is written to a chained,
tamper-evident record that can be replayed later. Nothing is
certified on the agent's say-so.

It works as four modules and one composed flow:

  • Apathy — the audit. Counts and claims are re-measured by a
    second, independent method before they are believed.
  • Proven — the verification. Capabilities are checked by live
    probes against the real system, not taken from a description.
  • Anchor — the certificate. Work that passed is certified;
    the certificate format and its verification are public.
  • Receipts — the record. A signed, chained ledger of what was
    checked and what was issued.
  • Flow — the composition: proposal in, certificate or named
    refusal out, receipt recorded.

Its place in the platform: the harness lives alongside the
toolset, not inside it. It is hosted outside the catalogue's
routers, so the 1,052 tools work exactly as before, and it uses
the same API keys and tiers. It is reachable over REST and MCP
under /api/trust/, with a public page at /trust.

Each judging lane's manual is delivered with its key, not published
here: GET /api/lane-manual with the lane's X-API-Key returns that
lane's manual, and only that lane's. The key selects the lane, so no
key can read another lane's manual, and access ends when the key
expires. See key-manuals/README.md.

Two further architecture implementations from the same programme
are not hosted endpoints, but can augment the architecture of
other systems and further automation:

  • Grantline — scoped, expiring, revocable credential grants:
    an agent uses a secret without ever possessing it.
  • Nightwatch — a human-gated automation protocol: work runs
    in verified batches, and a gate a human controls decides what
    proceeds.

Engineering summaries and code for both are available upon
request.

Both items that were mid-build at first publication are now
closed: Receipts answers over both REST and MCP (closed
2026-10-24), and Anchor live issuance is built and deployed
(2026-10-24) — a passing flow records its certificate in a
persisted live registry signed under a server-side key, and a
repeat certification is idempotent rather than duplicated.
Production issuance activates when the signing secret is
provisioned on Fly; until then the service self-reports live
issuance as unconfigured and resolves against the demonstration
registry, exactly as before. The toolset is unaffected.

The 9 Controlled Collisions

The beacon function frac(p × π/10 × 2³²) maps primes to 32-bit hex strings.
Nine primes are known to collide with the anchor value 1d2c7a5b:

# Prime Beacon output Role
1 P1 = 3000105001 1d2c7a5b Moat anchor
2 P2 = 5303687339 1d2c7a5b Moat anchor
3–9 Internal sieve primes 1d2c7a5b Commerce routing anchors

Why this is intentional: The moat design requires P1 and P2 to produce the same beacon value. This is what makes beacon verification deterministic. The collision bound for a random attacker is (9/4M)^35 ≈ 1e-197 — practically zero, but not a mathematical impossibility.


Tool Groups

Catalogue organization only — the four groups span the 21 blocks (MF-01–MF-21) and cross tier boundaries. Access is gated per block, not per group; see Access Tiers.

Group Tools Count
Market Router — payment, escrow, delivery, budget, notary 1–300 300
Math Engine — Arakelov, RH, BSD, Navier-Stokes, Yang-Mills, P vs NP 301–700 400
Amplum Everyday — scheduling, memory, legal, will, mesh treasury 701–1000 300
Brain Router — meta-tools that route the full catalogue: route, chain, think, swarm, consensus 1001–1052 52

Access Tiers

Tiers are cumulative. Each tier unlocks whole blocks at /api/mf/{block} — the labels below are exactly the gates enforced in code (ROUTERS in zerobeacon_mf_1000_main.py). Every block appears exactly once, so every tool carries its tier by construction.

Tier Monthly Tools (cumulative) Blocks unlocked
FREE $0 100 MF-01–MF-02
PRO $10 400 + MF-03–MF-08
PRO+ $100 800 + MF-09–MF-16
ENTERPRISE $199 1,052 + MF-17–MF-21

FREE tier: no API key required.
Paid tiers: pass X-API-Key: zbk_… header.
Get a key at https://zerobeacon.ai after Stripe checkout.

MCP note: tools/list exposes 1,003 operations — the 1,000 block tools (MF-01–MF-20) plus MF-21's brain, brain/fire, and brain/status. The remaining MF-21 endpoints are REST-only; that difference is the 1,052 catalogue vs 1,003 MCP counts above.


Connect

ZeroBeacon is a remote MCP server — no install, no proxy. Point any MCP client at the direct URL:```json
{"mcpServers":{"zerobeacon":{"url":"https://zerobeacon.ai/mcp"}}}


Free tier: the first 100 tools need no key. Paid tiers pass `X-API-Key: zbk_…` — get a key at https://zerobeacon.ai/pricing.

Also listed in the Smithery registry: https://smithery.ai/servers/davidjfox998/zerobeacon-1050

---

## 30-Second Self-Verification

Agents can verify the beacon anchor in one curl call:```bash
# 1. Verify the moat anchor — P1 must return beacon=1d2c7a5b
curl -s "https://zerobeacon.ai/api/mf/01/beacon?p=3000105001" | python3 -c "
import sys, json
d = json.load(sys.stdin)
assert d['beacon'] == '1d2c7a5b', f'Unexpected beacon: {d[\"beacon\"]}'
assert d['d'] == 2303582338,      f'Unexpected d: {d[\"d\"]}'
print('✓ P1 anchor verified:', d['beacon'])
"

# 2. Verify P2 anchor
curl -s "https://zerobeacon.ai/api/mf/01/beacon?p=5303687339" | python3 -c "
import sys, json
d = json.load(sys.stdin)
assert d['beacon'] == '1d2c7a5b', f'Unexpected beacon: {d[\"beacon\"]}'
print('✓ P2 anchor verified:', d['beacon'])
"

# 3. Verify genesis prime
curl -s "https://zerobeacon.ai/api/mf/01/beacon?p=82843" | python3 -c "
import sys, json
d = json.load(sys.stdin)
print('genesis beacon:', d['beacon'], '— d:', d['d'])
"

Expected output:```
✓ P1 anchor verified: 1d2c7a5b
✓ P2 anchor verified: 1d2c7a5b
genesis beacon: <value> — d: 2303582338


---

## Beacon Constants

| Constant | Value | Meaning |
|---|---|---|
| `beacon` | `1d2c7a5b` | Canonical anchor value at P1, P2 |
| `d` | `2303582338` | Discriminant — identifies this beacon chain |
| `genesis` | `82843` | First prime used in the chain |
| `P1` | `3000105001` | Moat anchor 1 |
| `P2` | `5303687339` | Moat anchor 2 |

---

## Authentication```http
GET /api/mf/01/beacon
X-API-Key: zbk_your_key_here

FREE tools (1–100): no key required.
Paid tools: key issued automatically after Stripe checkout at https://zerobeacon.ai

RapidAPI subscribers: use the RapidAPI gateway — no separate key needed.


Honest Claims

  • ✅ The beacon is collision-anchored at P1 and P2 (9 known collisions total)
  • ✅ The collision bound for random attackers is (9/4M)^35 ≈ 1e-197
  • ✅ Commerce routing decisions are deterministic given the anchor

Opera Numerorum Research Lab

The Math Engine (tools 301–700) implements numerical experiments related to:

  • Arakelov positivity — height bounds on arithmetic surfaces
  • Riemann Hypothesis descent — sieve residue structure mod 211
  • BSD conjecture — L-function analytic rank witnesses
  • Navier-Stokes — energy dissipation heuristics
  • Yang-Mills — mass gap numerical bounds
  • P vs NP — GapMCSP gap witness via 35-brother self-symmetry

These are computational tools for researchers, not machine-verified proofs.
Formal Lean 4 proofs live in the companion repos:
eutheos-property · p5-boundary · brothers-desert-proof


Health & Status```bash

curl -s https://zerobeacon.ai/health | python3 -m json.tool
```

Returns: Resend key status, RapidAPI secret status, uptime, tool count.


d=2303582338 · beacon=1d2c7a5b · genesis=82843

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
zerobeacon-1000-tool-collision-proof-commerce-router 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

zerobeacon-1000-tool-collision-proof-commerce-router 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

zerobeacon-1000-tool-collision-proof-commerce-router 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

zerobeacon-1000-tool-collision-proof-commerce-router 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

zerobeacon-1000-tool-collision-proof-commerce-router 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

zerobeacon-1000-tool-collision-proof-commerce-router 能提供哪些能力?

资料显示能力标签包括 ecommerce、commerce、mcp、mcp server、ai agents、paypal。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。