FairSeal MCP Server
OfficialFairseal 🦭
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.
Try It Now
npx @fairseal/commitOne command. A verifiable gacha pull in your terminal. No setup.
Related MCP server: garl
Quick Start
npm install @fairseal/commitimport { createCommitment, resolveCommitment, createReceipt, verifyReceipt } from '@fairseal/commit';
// 1. Lock your loot table BEFORE the outcome is knowable
const commitment = createCommitment({
rule: JSON.stringify(LOOT_TABLE),
inputs: [playerId, pullNumber.toString()],
revealAfter: 10,
});
// 2. Resolve with verifiable entropy from drand
const resolution = await resolveCommitment(commitment);
// 3. Your algorithm + verifiable entropy = provably fair drop
const drop = yourWeightedPull(LOOT_TABLE, resolution.beaconRandomness);
// 4. Package as a receipt anyone can verify
const receipt = createReceipt(commitment, resolution);
const proof = await verifyReceipt(receipt); // ✅ PARTIALHow It Works
Commit — Lock your drop table + player ID into a hash before the randomness exists
Entropy — Wait for a public drand beacon round (Cloudflare + Protocol Labs)
Resolve — Derive the selection from beacon entropy + your committed rule
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
Operation | Time |
Commitment creation | 0.006ms (170,000+/sec) |
Beacon fetch | ~200ms |
drand beacon verification (BLS12-381) | ~150ms |
Receipt size | 0.9 KB |
Client-side. No server. No account. No fees for PARTIAL verification.
Packages
Package | Description |
Game API for RGS studios. Slots, gacha, loot boxes. (v0.1 ALPHA) | |
Committed selection receipts. Core library. | |
Cryptographic primitives, signing, Merkle trees. | |
Independent receipt verification. | |
MCP server for AI agents. Verifiable entropy, provably-fair games, cryptographic receipt verification via Model Context Protocol. |
Use Cases
Scenario | How |
Gacha / loot box | Every pull has a receipt. Players verify drops match published rates. |
Boss loot drops | Drop table committed per encounter. No ninja-nerfing. |
Matchmaking | Pairing algorithm committed. Players verify no favoritism. |
Tournament brackets | Seeding provably random, not rigged. |
NFT mint order | Queue provably fair — no insider front-running. |
Slot machines | Seed 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 log | No one — receipts verify offline |
What is proven? | That an action was recorded | That a result was committed before the outcome was knowable |
Time proof | Server timestamp (operator-controlled) | External anchor on Base (independently checkable) |
Tamper evidence | Depends on log integrity | Hash-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
🌐 fairseal.io — Landing page
📦 npm @fairseal — All packages
🔍 verify.fairseal.io — Receipt verifier
📖 @fairseal/commit README — Full documentation
License
MIT — Fairseal
This server cannot be deployed
Maintenance
Related MCP Connectors
Attestable memory, truth, provenance. Hybrid Ed25519 + ML-DSA-65 receipts; USDC settlement on Base.
Trust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed.
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
Verify what an AI agent observed before it trusts, pays, or acts. FreshProof provides timestamped public URL observations, Proof Receipts, and policy verification, with paid x402 tools in USDC on Base.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceTamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.22 npm1MIT
garlofficial
AlicenseNot gradedqualityFmaintenanceCryptographic verification for AI agent actions — ECDSA-secp256k1 signed Action Receipts anchored on Base, multi-dimensional trust vectors, capability tokens, and offline-verifiable on-chain proof. 29 tools.2Apache 2.0- AlicenseAqualityBmaintenanceEnables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.1154 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceCryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.-