mcpField
F
fairseal-mcp-server

fairseal-mcp-server

Local
fairseal.ioGames & Entertainment0Updated 1w ago

About fairseal-mcp-server

fairseal-mcp-server exposes FairSeal’s verifiable randomness and receipt verification to AI agents, for game operators and systems that need auditable randomized outcomes. Its commit-before-outcome model lets results be independently checked.

Key features

  1. 01Verifiable entropy for selections
  2. 02Provably fair game outcomes
  3. 03Cryptographic receipt verification
  4. 04Commitment before outcome

Use cases

  1. 01Verify gacha and loot-box drops
  2. 02Audit randomized matchmaking
  3. 03Check tournament seeding
  4. 04Verify NFT mint queues

MCP support

Exposes verifiable entropy, provably fair games, and cryptographic receipt verification to AI agents through MCP.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"ned-del-fairseal": {
"command": "npx",
"args": [
"-y",
"@fairseal/mcp-server"
],
"env": {
"FAIRSEAL_API_KEY": "<FAIRSEAL_API_KEY>",
"FAIRSEAL_API_URL": "<FAIRSEAL_API_URL>"
}
}
}
}
Run commandnpx -y @fairseal/mcp-server
Environment variables to set
FAIRSEAL_API_KEYSecretOptional API key sent as Bearer header (live API currently requires no auth; any placeholder works).
FAIRSEAL_API_URLUpstream API base URL (default https://api.fairseal.io).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@fairseal/mcp-server0.1.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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

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.

Links

Listings

License

MIT — Fairseal

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.