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.

Postflop GTO Solver

MCPB · POSTFLOP-MCP.MCPB

Solve heads-up postflop poker spots with a GTO solver and query the solution

Available components

36 Trust /100

Last scanned (19 hours ago)

Scores higher than 70% of MCPB servers

Category Entertainment and Games

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
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 (AGPL-3.0-or-later).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 Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3158 tokens (~225/item across 14 items; 14 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (11)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (5)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 17 Nov 26 36

    First indexed and scored.

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 21 Nov 2026 · Analysed mcpb/https://github.com/sawadakaku/postflop-mcp/releases/download/v0.1.0/postflop-mcp.mcpb

Provenance No attestation

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

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 14 exposed · ~2,757 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
action_range ~138

The hands with which the player to act takes action (x / c / f / allin / b75, ...). Returns: the action's frequency, the breakdown by class and label, and the value/bluff split (value = equity of 50% or more against the opponent's whole range at this node).

NameTypeReqDescription
actionstringyesAction (x / c / f / allin / b75, ...)
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `

No output schema declared.

No examples provided.

bookmark ~126

Save, list or delete named branches. name and path save, name and delete=true delete, no arguments lists. Names have no spaces (e.g. A, line1). A saved branch expands when a path starts with #name (e.g. `#A x b75`).

NameTypeReqDescription
deleteboolean––
namestring–Bookmark name
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `

No output schema declared.

No examples provided.

compare_lines ~130

Compare two or more lines (paths, @sub3: ..., #A) side by side. For each line: player to act, pot, frequency and EV per action, and both players' overall equity. With hand (Ah8s / A8o), also that hand's frequencies, EV and equity (without player, the player to act in each line).

NameTypeReqDescription
handstring–Hand to compare (Ah8s / A8o)
linesarrayyes–
playerstring–Player: a name given in solve's names, or OOP / IP

No output schema declared.

No examples provided.

compare_stacks ~242

Re-solve the same node with only the stack depth changed and compare. Also saves a comparison view (HTML). Re-solves from the start of path's street (from the root of the spot with from_root=true). The first column is always the original solution. Always state the returned premise (where the stack was changed, and that earlier play used the original stack). With shallow stacks large bets merge into all-in, so some columns may not follow the path (error).

NameTypeReqDescription
from_rootboolean–If true, re-solve from the root of the spot (slower)
handstring–Hand to include (Ah8s / A8o)
pathstringyesNode path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `
playerstring–Player: a name given in solve's names, or OOP / IP
stacksarray–Effective stacks at the re-solve root, in bb. Defaults to SPR 1, 2 and 4

No output schema declared.

No examples provided.

exploit ~301

How to play if the opponent is biased. path is a node where the opponent acts (turn or river). Turn words like "bluffs too much" into concrete hands and strategy first (e.g. hands="K9s-K5s", strategy={"allin": 1}). The opponent keeps the original strategy except that hands play strategy; your best response is re-solved. Returns: ev_bb (GTO vs GTO / GTO vs biased / exploit vs biased / exploit vs GTO), gain_bb (what exploiting gains), risk_bb (what it loses if the opponent was not biased), hero_node (your frequencies after the opponent's then), assumption, notes and premise. Always state the assumption and premise.

NameTypeReqDescription
handstring–Your hand (Ah8s / A8o). Also returns how it plays in GTO and in the exploit
handsstringyesOpponent hands to bias (88-33 / A5s+ / KQo, ...)
pathstringyesNode path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `
strategyobjectyesFrequencies for those hands, e.g. {"allin": 1}
thenstring–The opponent action after which to show your node (default: the heaviest action in strategy)

No output schema declared.

No examples provided.

hand_detail ~170

Frequency, EV and equity of a hand for each action. hand is a combo (Ah8s) or a class (A8o / A8s / 88). A class lists each suit combination, which helps compare blockers. Without player, the player to act. For the player not to act, only EV and equity.

NameTypeReqDescription
handstringyesA combo (Ah8s) or a class (A8o / A8s / 88)
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `
playerstring–Player: a name given in solve's names, or OOP / IP

No output schema declared.

No examples provided.

lookahead ~101

Frequencies for the next few actions and the top classes taking each one. Stops at chance nodes; add a card to the path to look further.

NameTypeReqDescription
depthinteger–How many actions ahead (1-4, default 2)
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `

No output schema declared.

No examples provided.

node_info ~122

Who acts at this node, what they can do, and how the whole range plays. Returns: player to act, pot, stacks, amount to call, and per action the frequency (freq), combos and average EV (over the hands that take it), plus both players' overall equity. At a chance node, the cards that can come.

NameTypeReqDescription
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `

No output schema declared.

No examples provided.

range ~118

A player's range at this node: share and equity by hand class (top 20) and by made-hand label (full house, set, top pair, overpair, two pair on board (A kicker), ...).

NameTypeReqDescription
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `
playerstringyesPlayer: a name given in solve's names, or OOP / IP

No output schema declared.

No examples provided.

range_chart ~149

Save a player's range as a 13x13 hand chart (HTML). Use this to show a range instead of writing it out as a table. Show the user the returned file (send it if you can, otherwise give the path). For the player to act, each cell is colored by action frequencies and shows EVs when clicked. Otherwise cells are colored by equity.

NameTypeReqDescription
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `
playerstringyesPlayer: a name given in solve's names, or OOP / IP

No output schema declared.

No examples provided.

resolve_from ~382

Re-solve from the start of this node's street with changes (branches outside the tree). The start of the last street in path (right after its last card) becomes the root of the subgame. Earlier streets keep the original solution. Prefix a path with the returned sub (`@sub3: x b50`) to query the subgame with any tool. Always state the premise in your answer. From the river it takes under a second, from the turn seconds, from the flop tens of seconds to minutes.

NameTypeReqDescription
locksarray–Strategy locks, e.g. [{"hands": "88-33", "strategy": {"allin": 1}}]. Without path, the node given in path; with path, a path from the subgame root. Only the given hands are locked; the solver plays t…
pathstringyesNode path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `
rangesarray–Range changes, e.g. [{"player": "IP", "hands": "AK,AQ", "scale": 0}] (multiplies the reach; 0 removes the hands)
stack_bbnumber–Effective stack at the subgame root, in bb. To compare stack depths, compare_stacks is quicker
treeobject–Bet sizes per street as [OOP, IP] 'bet/raise' strings, e.g. {"turn": ["50%,75%/a", "33%,75%/a"]}. % is relative to the pot, a is all-in, 2.5x is a raise multiplier, and an empty "/" means check/call…

No output schema declared.

No examples provided.

solve ~473

Solve a spot (call this first; solving another spot replaces it). If the same spot was solved before, it loads from the cache in about a second. Otherwise it is solved and saved. From the river it takes under a second, from the turn seconds to tens of seconds, from the flop tens of seconds to minutes. Returns: the spot, the player names, the root node (same as node_info), the accuracy (exploitability_bb) and the memory used. With dry_run=true it only returns the memory needed, without solving.

NameTypeReqDescription
boardstringyes3 to 5 board cards, e.g. "QcQdJc" or "Qc Qd Jc 2d". The number of cards sets the starting street
dry_runboolean–If true, only return the memory needed (MB) without solving
ip_rangestringyesRange of IP (the player who acts last)
max_iterationsinteger–Maximum iterations (default 1000)
namesobject–Player names, e.g. {"oop": "BB", "ip": "BTN"}. Defaults to OOP / IP
oop_rangestringyesRange of OOP (the player who acts first), e.g. "AA-TT,AKs,A5s-A2s,KQo:0.5" (:0.5 is a weight; write ranges high to low: 99-22, AJo-A8o)
pot_bbnumberyesPot at the start of the street, in bb
stack_bbnumberyesEffective stack at the start of the street, in bb (what is left behind)
target_exploitability_pctnumber–Target accuracy as % of the pot (default 0.3). Smaller is more accurate and slower
treeobject–Bet sizes per street as [OOP, IP] 'bet/raise' strings, e.g. {"turn": ["50%,75%/a", "33%,75%/a"]}. % is relative to the pot, a is all-in, 2.5x is a raise multiplier, and an empty "/" means check/call…

No output schema declared.

No examples provided.

suit_chart ~142

Save a table (HTML) of every suit combination of a hand class (A8o / A8s / 88) of the player to act. Shows each combo's frequencies, EV and equity, and how much of the opponent's value and bluffs it blocks. Use it to explain blockers, and show the user the returned file.

NameTypeReqDescription
handstringyesHand class (A8o / A8s / 88)
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `

No output schema declared.

No examples provided.

tree_view ~163

Save the next few actions from this node as a clickable game tree (HTML). Clicking a node shows the player to act, the pot, frequencies and EVs per action, and both players' 13x13 range charts. Use it for "what happens next?" or "show me this line", and show the user the returned file. Stops at chance nodes and terminal nodes. Call it again with a card added to the path to go further.

NameTypeReqDescription
depthinteger–How many actions ahead (1-4, default 3)
pathstring–Node path, e.g. `x b75 c / Js / x`. Empty for the root of the spot. May start with `@sub3: ` or `#A `

No output schema declared.

No examples provided.

Install

How do I install the Postflop GTO Solver MCP server?

Postflop GTO Solver ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 3650c6d6d4f5aa494b57ea91e9b3e6fa158dea8077f9fce958765eca6416bee0; the commands to do that are on this page. If it does not match, do not open it.

mcpb · postflop-mcp.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

3650c6d6d4f5aa494b57ea91e9b3e6fa158dea8077f9fce958765eca6416bee0

macOS / Linux

echo "3650c6d6d4f5aa494b57ea91e9b3e6fa158dea8077f9fce958765eca6416bee0  postflop-mcp.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\postflop-mcp.mcpb).Hash -eq "3650c6d6d4f5aa494b57ea91e9b3e6fa158dea8077f9fce958765eca6416bee0"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Postflop GTO Solver MCP server?

Postflop GTO Solver is an MCP server listed in the public MCP registry as io.github.sawadakaku/postflop-mcp. Solve heads-up postflop poker spots with a GTO solver and query the solution. This page covers its MCPB bundle (https://github.com/sawadakaku/postflop-mcp/releases/download/v0.1.0/postflop-mcp.mcpb).

Is the Postflop GTO Solver MCP server safe to use?

Postflop GTO Solver scores 36 out of 100 on VerifyMCP. 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 Postflop GTO Solver MCP server expose?

Postflop GTO Solver exposes 14 tools: solve, node_info, hand_detail, range, action_range, and 9 more. Their descriptions and schemas cost roughly 2,757 tokens of context every time the server is loaded.

What licence is the Postflop GTO Solver MCP server under?

Postflop GTO Solver declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Postflop GTO Solver MCP server?

VerifyMCP ran 11 checks on Postflop GTO Solver, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about Postflop GTO Solver: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.