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 分