Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.fairseal/mcp-server

NPM · @FAIRSEAL/MCP-SERVER

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

0 this week 77 Trust /100

Last scanned (20 hours ago)

Scores higher than 55% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1243 tokens (~77/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/@fairseal/mcp-server@0.2.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,243 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fairseal_anchor_status ~69

Check anchor lifecycle by anchor_id (GET /v2/anchor/{id}, live service). Free, no key needed. Lifecycle: queued → batched → anchored (Merkle proof + Base mainnet tx hash).

NameTypeReqDescription
anchor_idstringyesAnchor ID from fairseal_anchor_submit

No output schema declared.

No examples provided.

fairseal_anchor_submit ~147

Queue a SHA-256 hash for Merkle-batch anchoring to Base mainnet (POST /v2/anchor, live service at x402.fairseal.io). Returns anchor_id + status_url; poll with fairseal_anchor_status until 'anchored' (typically ~60s). Auth: Bearer key (FAIRSEAL_API_KEY / FAIRSEAL_ANCHOR_API_KEY) or keyless x402 USDC micropayment (an HTTP 402 response carries machine-readable payment terms).

NameTypeReqDescription
metadataobject–Optional metadata object stored with the submission
payload_hashstringyesSHA-256 hex digest of the receipt/commitment to anchor

No output schema declared.

No examples provided.

fairseal_dice_bet ~83

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

NameTypeReqDescription
amountnumber––
bet_typestringyes–
player_idstring––
player_seedstring––
targetinteger–Target sum for exact bets

No output schema declared.

No examples provided.

fairseal_entropy ~39

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fairseal_gacha_pull ~52

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

NameTypeReqDescription
player_idstring––
player_seedstring––
poolstring––

No output schema declared.

No examples provided.

fairseal_game_result ~93

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

NameTypeReqDescription
game_idstringyesGame ID — 64-char hex hash, e.g. 64096a172374489ccd4563d7c15efe5e467604dd826149da0511a0fa6109e26f (get one from fairseal_recent_games or a bet tool response)

No output schema declared.

No examples provided.

fairseal_games_catalog ~37

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fairseal_hash_content ~80

Compute the SHA-256 hex digest of a string locally. Zero network calls — the content never leaves this machine. Use it to hash an agent's input and decision text before notarizing, so only hashes (never raw content) are sent to FairSeal.

NameTypeReqDescription
contentstringyesContent to hash (UTF-8). Never transmitted anywhere.

No output schema declared.

No examples provided.

fairseal_notarize_decision ~245

Create a cryptographic receipt for an AI-agent decision (POST /v1/notarize, schema agent_decision). The receipt is Merkle-batched and anchored on Base mainnet; verify offline with @fairseal/verify or at the returned verify_url. Receipts prove provenance (this hash existed at this time), not correctness of the decision. [requires FAIRSEAL_API_KEY or FAIRSEAL_NOTARY_API_KEY]

NameTypeReqDescription
agent_idstringyesStable identifier of the deciding agent
decided_atstring–ISO-8601 UTC timestamp of the decision; defaults to now
decision_hashstringyesSHA-256 hex of the decision content (use fairseal_hash_content)
descriptionstring–Optional human-readable description
input_hashstringyesSHA-256 hex of the decision input (use fairseal_hash_content)
modelstring–Optional model identifier
operatorstring–Optional operator identifier
payload_hashstring–SHA-256 hex of the full payload being notarized; defaults to decision_hash
session_idstring–Optional session identifier

No output schema declared.

No examples provided.

fairseal_notarize_status ~78

Fetch a notarization receipt by receipt_id (GET /v1/notarize/{id}). Free, no key needed. Returns the receipt, Merkle proof, and on-chain anchor tx once status is 'anchored'.

NameTypeReqDescription
receipt_idstringyesReceipt ID from fairseal_notarize_decision (nr_...)

No output schema declared.

No examples provided.

fairseal_recent_games ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fairseal_rng_generate ~59

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

NameTypeReqDescription
client_seedstring–Optional client-provided seed

No output schema declared.

No examples provided.

fairseal_sicbo_bet ~108

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

NameTypeReqDescription
amountnumber––
bet_typestringyes–
comboarray–Dice combination for combo bets
player_idstring––
player_seedstring––
targetinteger–Target value (total/single/double/triple bets)

No output schema declared.

No examples provided.

fairseal_slots_spin ~55

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

NameTypeReqDescription
amountnumber––
player_idstring––
player_seedstring––

No output schema declared.

No examples provided.

fairseal_stats ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fairseal_verify_game ~45

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

NameTypeReqDescription
game_idstringyesGame ID to verify

No output schema declared.

No examples provided.

Install

How do I install the io.fairseal/mcp-server server?

io.fairseal/mcp-server runs locally as an npm package, launched with npx -y @fairseal/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @fairseal/mcp-server

# add to Claude Code
claude mcp add io-fairseal-mcp-server -- npx -y @fairseal/mcp-server
Common questions

What is the io.fairseal/mcp-server server?

io.fairseal/mcp-server is listed in the public MCP registry as io.fairseal/mcp-server. Verifiable entropy, provably-fair games, and receipt verification for AI agents (FairSeal API). This page covers its npm package (@fairseal/mcp-server).

Is the io.fairseal/mcp-server server safe to use?

io.fairseal/mcp-server scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.fairseal/mcp-server server expose?

io.fairseal/mcp-server exposes 16 tools: fairseal_entropy, fairseal_games_catalog, fairseal_stats, fairseal_recent_games, fairseal_game_result, and 11 more. Their descriptions and schemas cost roughly 1,243 tokens of context every time the server is loaded.

Is the io.fairseal/mcp-server server still maintained?

io.fairseal/mcp-server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.fairseal/mcp-server server under?

io.fairseal/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.