io.github.ned-del/fairseal-mcp-server
NPM · @FAIRSEAL/MCP-SERVER · SCANNED SEP 20
Verifiable entropy, provably-fair games, and receipt verification for AI agents (FairSeal API).
Available components
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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 768 tokens (~59/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the io.github.ned-del/fairseal-mcp-server server?
io.github.ned-del/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
claude mcp add ned-del-fairseal-mcp-server -- npx -y @fairseal/mcp-server
{
"mcpServers": {
"ned-del-fairseal-mcp-server": {
"command": "npx",
"args": [
"-y",
"@fairseal/mcp-server"
]
}
}
} {
"servers": {
"ned-del-fairseal-mcp-server": {
"command": "npx",
"args": [
"-y",
"@fairseal/mcp-server"
]
}
}
} codex mcp add ned-del-fairseal-mcp-server -- npx -y @fairseal/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ned-del-fairseal-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@fairseal/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add ned-del-fairseal-mcp-server --command npx --arg -y --arg @fairseal/mcp-server
mcp_servers:
ned-del-fairseal-mcp-server:
command: "npx"
args: ["-y", "@fairseal/mcp-server"] {
"McpServers": {
"ned-del-fairseal-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@fairseal/mcp-server"
]
}
}
} assistant mcp add ned-del-fairseal-mcp-server -t stdio -c npx -a -y @fairseal/mcp-server
{
"mcpServers": {
"ned-del-fairseal-mcp-server": {
"command": "npx",
"args": [
"-y",
"@fairseal/mcp-server"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 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.
- 5 Sept 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.
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 20 Sept 2026 · Analysed npm/@fairseal/mcp-server@0.1.3
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
fairseal_anchor_status Anchor status (preview stub) ~70
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).
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | Anchor ID from fairseal_anchor_submit |
No output schema declared.
No examples provided.
fairseal_anchor_submit Submit anchor (preview stub) ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payload_hash | string | yes | SHA-256 hex digest of the receipt/commitment to anchor |
No output schema declared.
No examples provided.
fairseal_dice_bet Place Dice bet ~83
Place a two-dice bet (exact/over7/under7/odd/even). Resolves after next epoch (~5s).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| bet_type | string | yes | – |
| player_id | string | – | – |
| player_seed | string | – | – |
| target | integer | – | Target sum for exact bets |
No output schema declared.
No examples provided.
fairseal_entropy Get verifiable 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 Gacha pull ~52
Pull a weighted loot box (standard or premium pool). Provably fair via VDF.
| Name | Type | Req | Description |
|---|---|---|---|
| player_id | string | – | – |
| player_seed | string | – | – |
| pool | string | – | – |
No output schema declared.
No examples provided.
fairseal_game_result Get game result ~93
Fetch the result of a game by game_id (poll until resolved). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| game_id | string | yes | Game 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 List FairSeal games ~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_recent_games 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 Generate verifiable RNG ~59
Request raw verifiable random number generation (resolves after next VDF epoch, ~5s). Returns a poll URL / game_id. [requires FAIRSEAL_API_KEY]
| Name | Type | Req | Description |
|---|---|---|---|
| client_seed | string | – | Optional client-provided seed |
No output schema declared.
No examples provided.
fairseal_sicbo_bet Place Sic Bo 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| bet_type | string | yes | – |
| combo | array | – | Dice combination for combo bets |
| player_id | string | – | – |
| player_seed | string | – | – |
| target | integer | – | Target value (total/single/double/triple bets) |
No output schema declared.
No examples provided.
fairseal_slots_spin Slots spin ~55
Spin the 5-reel 3-row slot machine with wild substitution. Provably fair via VDF.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| player_id | string | – | – |
| player_seed | string | – | – |
No output schema declared.
No examples provided.
fairseal_stats Engine 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 Verify game fairness ~45
Verify the fairness of a completed game. Returns VDF proof data and replay steps for independent verification. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| game_id | string | yes | Game ID to verify |
No output schema declared.
No examples provided.
What is the io.github.ned-del/fairseal-mcp-server server?
io.github.ned-del/fairseal-mcp-server is listed in the public MCP registry as io.github.ned-del/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.github.ned-del/fairseal-mcp-server server safe to use?
io.github.ned-del/fairseal-mcp-server scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.github.ned-del/fairseal-mcp-server server expose?
io.github.ned-del/fairseal-mcp-server exposes 13 tools: fairseal_entropy, fairseal_games_catalog, fairseal_stats, fairseal_recent_games, fairseal_game_result, and 8 more. Their descriptions and schemas cost roughly 768 tokens of context every time the server is loaded.
Is the io.github.ned-del/fairseal-mcp-server server still maintained?
io.github.ned-del/fairseal-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 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.github.ned-del/fairseal-mcp-server server under?
io.github.ned-del/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.