Fairseal Mcp Server

io.github.ned-del由 GitHub 账号 ned-del 发布v0.1.3更新于 Oct 24, 2026

Verifiable entropy, provably-fair games, and receipt verification for AI agents (FairSeal API).

已验证STDIO仅桌面金融安全与监控AI 与机器学习

概览

AI 生成的概览

让助手使用公共 drand 熵源创建并验证可证明公平的选择收据，适用于游戏、战利品箱和随机分配。

可以做什么
FairSeal 为 AI 代理提供可验证熵、可证明公平的游戏机制和加密收据验证。它会在随机性产生之前将规则和输入提交为哈希，使用公共 drand 信标轮次解析选择，并将结果打包为任何人都能离线重跑和验证的收据。收据签名使用 EIP-191（secp256k1）或 Ed25519，而 drand 信标签名使用 BLS12-381 验证。
适用场景
当助手需要做出或审计必须可证明公平且可独立验证的随机选择时使用，例如抽卡、战利品掉落、匹配、锦标赛种子、NFT 铸造顺序或老虎机旋转。它也适用于公证某个结果在结果可知之前已被提交。
运行要求
作为本地 stdio 进程运行，通常通过 npm 包 @fairseal/mcp-server。可选的 FAIRSEAL_API_KEY 可作为 Bearer 头发送，但实时 API 目前不需要认证，任何占位符都可用。上游 API 基础 URL 默认为 FAIRSEAL_API_URL 覆盖。获取 drand 信标轮次需要网络访问。
安装前请注意
可选的 FAIRSEAL_API_KEY 是作为 Bearer 头发送的机密，即使实时 API 目前接受占位符，也应视为敏感信息。收据在 Base 上进行外部锚定，README 说明 FairSeal 通过 Coinbase 的 x402 结算小额支付，因此可能涉及支付或链上活动。README 示例中将验证描述为 PARTIAL，因此在依赖收据之前请确认它实际证明了什么。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Fairseal Mcp Server，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Fairseal 🦭

Provably fair selections for games, loot boxes, and any randomized allocation.

Fairseal creates verifiable receipts (CSRs) proving that a selection was committed before the outcome was knowable. Every loot drop, gacha pull, and randomized selection — independently verifiable, trustlessly.

[@fairseal/commit] [@fairseal/core]

Try It Now

bash
npx @fairseal/commit

One command. A verifiable gacha pull in your terminal. No setup.

Quick Start

bash
npm install @fairseal/commit
typescript
import { createCommitment, resolveCommitment, createReceipt, verifyReceipt } from '@fairseal/commit';
// 1. Lock your loot table BEFORE the outcome is knowableconst commitment = createCommitment({  rule: JSON.stringify(LOOT_TABLE),  inputs: [playerId, pullNumber.toString()],  revealAfter: 10,});
// 2. Resolve with verifiable entropy from drandconst resolution = await resolveCommitment(commitment);
// 3. Your algorithm + verifiable entropy = provably fair dropconst drop = yourWeightedPull(LOOT_TABLE, resolution.beaconRandomness);
// 4. Package as a receipt anyone can verifyconst receipt = createReceipt(commitment, resolution);const proof = await verifyReceipt(receipt); // ✅ PARTIAL

How It Works

  1. Commit — Lock your drop table + player ID into a hash before the randomness exists
  2. Entropy — Wait for a public drand beacon round (Cloudflare + Protocol Labs)
  3. Resolve — Derive the selection from beacon entropy + your committed rule
  4. Verify — Anyone can re-run every step. drand beacon signatures are BLS12-381-verified; FairSeal receipt signatures use EIP-191 (secp256k1) / Ed25519 — receipts are never BLS-signed. No trust required.

Performance

OperationTime
Commitment creation0.006ms (170,000+/sec)
Beacon fetch~200ms
drand beacon verification (BLS12-381)~150ms
Receipt size0.9 KB

Client-side. No server. No account. No fees for PARTIAL verification.

Packages

PackageDescription
@fairseal/gameGame API for RGS studios. Slots, gacha, loot boxes. (v0.1 ALPHA)
@fairseal/commitCommitted selection receipts. Core library.
@fairseal/coreCryptographic primitives, signing, Merkle trees.
@fairseal/verifyIndependent receipt verification.
@fairseal/mcp-serverMCP server for AI agents. Verifiable entropy, provably-fair games, cryptographic receipt verification via Model Context Protocol.

Use Cases

ScenarioHow
Gacha / loot boxEvery pull has a receipt. Players verify drops match published rates.
Boss loot dropsDrop table committed per encounter. No ninja-nerfing.
MatchmakingPairing algorithm committed. Players verify no favoritism.
Tournament bracketsSeeding provably random, not rigged.
NFT mint orderQueue provably fair — no insider front-running.
Slot machinesSeed Commitment Model — verifiable spins, no nonce chain.

Result Notarization vs. Activity Receipts

Most "agent receipts" today are activity receipts: the platform logs what an agent did, and you trust whoever wrote the log. Fairseal receipts are result notarization — a different trust model:

Activity receipts (platform logs)Fairseal result notarization
Who do you trust?The operator writing the logNo one — receipts verify offline
What is proven?That an action was recordedThat a result was committed before the outcome was knowable
Time proofServer timestamp (operator-controlled)External anchor on Base (independently checkable)
Tamper evidenceDepends on log integrityHash-anchored; any modification breaks verification

Related standards: payment-authorization protocols like Google/Mastercard AP2 (mandates), Visa TAP, and OpenAI/Stripe ACP prove that an agent may act and who it is. Fairseal proves what happened — that a result was committed and hasn't been altered since. Fairseal settles micropayments over Coinbase's x402 and does not implement AP2/TAP/ACP; the layers are complementary.

Links

Listings

License

MIT — Fairseal

来源：README.md，提交 73043e8

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.1.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分