Skip to content
PokerInk logo

PokerInk MCP server

Which MCP servers are PokerInk's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to PokerInk

Whose server it is
  • Registry namecom.pokerink/poker-toolsverified in the MCP registry

The registry name sits under pokerink.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools3
  • Server calls itselfpokerink-poker-tools
  • Server version1.2.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 32 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Log poker hands by speaking or typing them; Drill the spots you most often get wrong.

Once connected

  • Parameters are untyped or undescribed in 1 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 15, the first on 2026-10-21
  • INITE MCP score71 of 100answers 100 · does the job 0 · definitions 94 · context 100 · connects 100
  • What an agent can do with it0 of 2 use cases
  • Answered100% of days15 of 15 daily checks
  • Median first answer109 ms
  • Space in an agent's context≈ 676 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 94 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 3

What an agent can do with it

  • cannot · Log poker hands by speaking or typing them
  • not sure · Review leaks in your own play with AI analysis
  • cannot · Drill the spots you most often get wrong

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-21
  • calculate_equity

    Texas Hold'em or Pot Limit Omaha equity for 2-4 specific hands on 0-5 community cards, returning win, tie, and total equity percentages per hand. Hold'em enumerates every remaining board runout (no simulation). Omaha (game: "omaha"…

  • analyze_hand

    Read one Texas Hold'em hand on a 3-5 card board: the made hand (category and label) plus every draw with its out count.

  • calculate_pot_odds

    Decide whether calling a bet is profitable. Returns the pot odds, the equity needed to break even, and — given an out count — the exact chance of hitting and a call/fold verdict. Use this instead of doing the arithmetic: the break-even…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "poker-tools": {
      "type": "http",
      "url": "https://pokerink.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http pokerink https://pokerink.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://pokerink.com/api/mcp as a custom connector in the settings.

OpenAPI spec

3 paths, read 2026-10-21. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.