English Français العربية

io.fairseal/mcp-server

Registre officiel Jeux, sport et divertissement

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

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @fairseal/mcp-server
Claude Code 
claude mcp add io-fairseal-mcp-server -e 'FAIRSEAL_API_KEY=<your fairseal_api_key>' -e 'FAIRSEAL_API_URL=<FAIRSEAL_API_URL>' -e 'FAIRSEAL_NOTARY_API_KEY=<your fairseal_notary_api_key>' -e 'FAIRSEAL_ANCHOR_API_KEY=<your fairseal_anchor_api_key>' -- npx -y @fairseal/mcp-server@0.2.4
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "io-fairseal-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@fairseal/mcp-server@0.2.4"
            ],
            "env": {
                "FAIRSEAL_API_KEY": "<your fairseal_api_key>",
                "FAIRSEAL_API_URL": "<FAIRSEAL_API_URL>",
                "FAIRSEAL_NOTARY_API_KEY": "<your fairseal_notary_api_key>",
                "FAIRSEAL_ANCHOR_API_KEY": "<your fairseal_anchor_api_key>"
            }
        }
    }
}

Variables d'environnement

  • FAIRSEAL_API_KEY secret API key for gated tools (fairseal_entropy, fairseal_stats, fairseal_rng_generate, fairseal_notarize_decision, fairseal_anchor_submit). Key prefix: fsn_. Without a key these tools return 401; free tools (game reads, notarize_status, anchor_status) work without any key. x402 micropayment ($0.02 USDC on Base) is an alternative to the key for notarize/anchor.
  • FAIRSEAL_API_URL Upstream API base URL (default https://api.fairseal.io).
  • FAIRSEAL_NOTARY_API_KEY secret Key override for the notary service only (POST /v1/notarize). Falls back to FAIRSEAL_API_KEY if not set. Key prefix: fsn_.
  • FAIRSEAL_ANCHOR_API_KEY secret Key override for Anchor API v2 only (POST /v2/anchor). Falls back to FAIRSEAL_API_KEY if not set. Key prefix: anck_.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Fairseal 🦭
  2. Try It Now
  3. Quick Start
  4. How It Works
  5. Performance
  6. Packages
  7. Use Cases
  8. Result Notarization vs. Activity Receipts
  9. Links
  10. Listings
  11. License

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.

Try It Now

npx @fairseal/commit

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

Quick Start

npm install @fairseal/commit
import { 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); // ✅ 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.

Listings

License

MIT — Fairseal

Questions fréquentes

Qu'est-ce que io.fairseal/mcp-server ?

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

Comment installer io.fairseal/mcp-server ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add io-fairseal-mcp-server -e 'FAIRSEAL_API_KEY=<your fairseal_api_key>' -e 'FAIRSEAL_API_URL=<FAIRSEAL_API_URL>' -e 'FAIRSEAL_NOTARY_API_KEY=<your fairseal_notary_api_key>' -e 'FAIRSEAL_ANCHOR_API_KEY=<your fairseal_anchor_api_key>' -- npx -y @fairseal/mcp-server@0.2.4. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.fairseal/mcp-server ?

Oui. Il attend FAIRSEAL_API_KEY, FAIRSEAL_NOTARY_API_KEY, FAIRSEAL_ANCHOR_API_KEY, à renseigner dans sa configuration.

io.fairseal/mcp-server est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.fairseal/mcp-server ?

Il est publié par ned-del. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.