Pokerai API
NPM · @POKERAI/MCP
Solver-grade GTO strategy for study. Real-time assistance (RTA) at real-money tables is prohibited.
Available components
Last scanned (10 hours ago)
Scores higher than 33% of npm servers
Category Entertainment and Games
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 693 tokens (~138/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 122 → 138 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.2 → 0.1.3 functional
- 31 Oct 26 49
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pokerai/mcp@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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
flop_node Flop node strategy ~85
Strategy at one flop decision-tree node. Pass a `node` token minted by flop_tree. With hole_cards → that hand's mixed strategy at the node; omit → the node's whole-range strategy. Free (token-gated).
| Name | Type | Req | Description |
|---|---|---|---|
| hole_cards | string | – | optional hero hand, e.g. 'AdKd' |
| node | string | yes | node token from flop_tree |
No output schema declared.
No examples provided.
flop_tree Flop decision tree ~221
Starting ranges + every decision node for a flop spot. In the response each node has `node`, its path (e.g. root/CHECK), and `token`; pass `token` as the `node` argument of flop_node. Charges 1 presolved quota. Single-street (for turn/river use the solver tools).
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | the 3 flop cards, e.g. '2c2h2s' |
| flop_version | string | – | flop dataset id, same values as preflop_versions; omit for the default dataset (6max). Some boards have no data in the default dataset: the call returns 404 and still charges 1 presolved quota, so re… |
| positions | object | yes | roles→positions. SRP: {hero,raiser,caller}; 3BET/4BET: {hero,raiser,three_bettor}; LIMP: {hero,limper} (hero or limper must be BB) |
| pot_type | string | yes | – |
No output schema declared.
No examples provided.
preflop_range Whole preflop range for a spot ~150
The full 169-hand-type range (fold/call/raise per hand type: AA, AKs, AKo, ...) for a position + action line. No hole_cards. Charges 1 presolved quota (one call, not 169).
| Name | Type | Req | Description |
|---|---|---|---|
| hero | string | yes | the position whose range you want: UTG / MP / CO / BTN / SB / BB |
| preflop_actions | array | yes | action sequence incl. blinds; the range is for `hero` acting after these actions |
| preflop_version | string | – | chart-set id from preflop_versions; omit for the default |
| table_size | string | – | defaults to '6max' |
No output schema declared.
No examples provided.
preflop_strategy Preflop GTO strategy for a hand ~195
GTO mixed strategy (fold/call/raise frequencies + sizes) for a specific hand facing a preflop action line, 6-max 100bb. Charges 1 presolved quota. The situation (RFI/3-bet/4-bet/...) is derived from the actions.
| Name | Type | Req | Description |
|---|---|---|---|
| hero | string | yes | hero position: UTG / MP / CO / BTN / SB / BB |
| hole_cards | string | yes | hero's two cards, e.g. 'AhKh' |
| preflop_actions | array | yes | full action sequence including blinds, e.g. [{position:'SB',action:'small blind',amount:0.5},{position:'BB',action:'big blind',amount:1},{position:'UTG',action:'raise',amount:3}] |
| preflop_version | string | – | chart-set id from preflop_versions; omit for the default |
No output schema declared.
No examples provided.
preflop_versions List preflop strategy versions ~42
The selectable preflop_version values (id + human label) and which is the default. Free (no quota). Call this before assuming a version id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Pokerai API MCP server?
Pokerai API runs locally as an npm package, launched with npx -y @pokerai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pokerai/mcp
claude mcp add pokerai-bet-mcp -- npx -y @pokerai/mcp
What is the Pokerai API MCP server?
Pokerai API is an MCP server listed in the public MCP registry as io.github.pokerai-bet/mcp. Solver-grade GTO strategy for study. Real-time assistance (RTA) at real-money tables is prohibited. This page covers its npm package (@pokerai/mcp).
Is the Pokerai API MCP server safe to use?
Pokerai API scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 Pokerai API MCP server expose?
Pokerai API exposes 5 tools: preflop_versions, preflop_strategy, preflop_range, flop_tree, flop_node. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.
Is the Pokerai API MCP server still maintained?
Pokerai API is still listed as active in the MCP registry. We last reached this channel on 5 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 Pokerai API MCP server under?
Pokerai API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.