Remote MCP · Endpoint

PokerData MCP server

No. PokerData answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://pokerdata.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.hft-studio/pokerdata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
GTO poker solver data: NLHE/PLO preflop ranges, postflop strategy, EV. 6-max NL preflop free.
Listing
From the official MCP registry (active).
Recent checks of PokerData
CheckedResultHandshake
5 hours agoHandshake completed148 ms
9 days agoHandshake completed193 ms
10 days agoHandshake completed138 ms
11 days agoHandshake completed128 ms
12 days agoHandshake completed371 ms
14 days agoHandshake completed179 ms
14 days agoHandshake completed165 ms
15 days agoHandshake completed146 ms
17 days agoHandshake completed164 ms
19 days agoHandshake completed443 ms
21 days agoHandshake completed121 ms
24 days agoHandshake completed138 ms
26 days agoHandshake completed142 ms
28 days agoHandshake completed95 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with PokerData and makes no claim about it beyond what these checks measured.