@fairseal/mcp-server

MCPcommunity
v0.2.3FairSealMITUpdated 8d agonpmGitHub

MCP server for FairSeal — verifiable entropy, provably-fair games, and cryptographic receipt verification for AI agents (stdio transport).

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
238Downloads/wk
8d agoLast update
Reads these credentials
  • FAIRSEAL_API_KEYAPI keyoptional

    Optional API key sent as Bearer header (live API currently requires no auth; any placeholder works).

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorFairSeal
LicenseMIT
Version0.2.3
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface13 tools · none privileged
Security scan✓ Cleanv0.1.3 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

13 tools · none privileged
Statically extracted from the published packagev0.1.3 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

fairseal_entropyFetch raw verifiable entropy from the latest resolved VDF epoch at api.fairseal.io. Read-only. [requires FAIRSEAL_API_KEY]

Fetch raw verifiable entropy from the latest resolved VDF epoch at api.fairseal.io. Read-only. [requires FAIRSEAL_API_KEY]

No input schema was published for this tool.

fairseal_games_catalogList available provably-fair games (sicbo, dice, gacha, slots) with bet types and endpoints. Read-only.

List available provably-fair games (sicbo, dice, gacha, slots) with bet types and endpoints. Read-only.

No input schema was published for this tool.

fairseal_statsFairSeal entropy engine statistics. Read-only. [requires FAIRSEAL_API_KEY]

FairSeal entropy engine statistics. Read-only. [requires FAIRSEAL_API_KEY]

No input schema was published for this tool.

fairseal_recent_gamesList recently resolved games (useful to find game_ids to verify). Read-only.

List recently resolved games (useful to find game_ids to verify). Read-only.

No input schema was published for this tool.

fairseal_game_resultFetch the result of a game by game_id (poll until resolved). Read-only.

Fetch the result of a game by game_id (poll until resolved). Read-only.

No input schema was published for this tool.

fairseal_verify_gameVerify the fairness of a completed game. Returns VDF proof data and replay steps for independent verification. Read-only.

Verify the fairness of a completed game. Returns VDF proof data and replay steps for independent verification. Read-only.

No input schema was published for this tool.

fairseal_rng_generateRequest raw verifiable random number generation (resolves after next VDF epoch, ~5s). Returns a poll URL / game_id. [requires FAIRSEAL_API_KEY]

Request raw verifiable random number generation (resolves after next VDF epoch, ~5s). Returns a poll URL / game_id. [requires FAIRSEAL_API_KEY]

No input schema was published for this tool.

fairseal_sicbo_betPlace a three-dice Sic Bo bet. Outcomes provably fair via VDF. Resolves after next epoch (~5s); use fairseal_game_result to poll.

Place a three-dice Sic Bo bet. Outcomes provably fair via VDF. Resolves after next epoch (~5s); use fairseal_game_result to poll.

No input schema was published for this tool.

fairseal_dice_betPlace a two-dice bet (exact/over7/under7/odd/even). Resolves after next epoch (~5s).

Place a two-dice bet (exact/over7/under7/odd/even). Resolves after next epoch (~5s).

No input schema was published for this tool.

fairseal_gacha_pullPull a weighted loot box (standard or premium pool). Provably fair via VDF.

Pull a weighted loot box (standard or premium pool). Provably fair via VDF.

No input schema was published for this tool.

fairseal_slots_spinSpin the 5-reel 3-row slot machine with wild substitution. Provably fair via VDF.

Spin the 5-reel 3-row slot machine with wild substitution. Provably fair via VDF.

No input schema was published for this tool.

fairseal_anchor_submitPREVIEW STUB of the future Anchor API v2 (POST /v2/anchor). Simulates queuing a commitment hash for Merkle-batch anchoring to Base. No payment, no chain writes.

PREVIEW STUB of the future Anchor API v2 (POST /v2/anchor). Simulates queuing a commitment hash for Merkle-batch anchoring to Base. No payment, no chain writes.

No input schema was published for this tool.

fairseal_anchor_statusPREVIEW STUB of the future Anchor API v2 (GET /v2/anchor/{id}). Each poll advances the simulated lifecycle: queued → batched (Merkle proof) → anchored (simulated tx hash).

PREVIEW STUB of the future Anchor API v2 (GET /v2/anchor/{id}). Each poll advances the simulated lifecycle: queued → batched (Merkle proof) → anchored (simulated tx hash).

No input schema was published for this tool.

13 of 13 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for FairSeal — verifiable entropy, provably-fair games, and cryptographic receipt verification for AI agents (stdio transport).

Keywords
mcpmodel-context-protocolfairsealverifiable-randomnessvdfprovably-fairentropyai-agentsx402receipts
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.