MCP servers observed by Lowdown
io.github.hft-studio/pokerdata MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 33 tools listed. On 2026-11-15 a tool description with a URL appeared (new domain: docs.pokerdata.io). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.hft-studio/pokerdata
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.hft-studio/pokerdata?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed; tool count 32 → 33; a tool description with a URL appeared (docs.pokerdata.io)
What tools does it list?
33 tools on 2026-11-18:
compare_strategiesenqueue_solveexplain_combofind_handsget_board_reportget_configget_exploitabilityget_hand_resultsget_nodeget_opponent_limp_rangeget_opponent_notesget_postflop_nodeget_postflop_rangeget_pricingget_queued_solveget_rangeget_range_metadataget_session_summaryget_startedget_tournament_resultsget_tree_docsget_upload_linklist_datasetslist_gameslist_library_solutionslist_my_opponentslist_my_requestslist_my_sessionslist_postflop_packslist_queued_solveslist_spotssubmit_requestupload_hand_history
MCP Registry declaration
- Registry name:
io.github.hft-studio/pokerdata - Declared version: 1.0.4
- Status: active
- Declared hosts:
pokerdata.io
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.hft-studio/pokerdata", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.hft-studio/pokerdata?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.hft-studio/pokerdata -- npx -y pokerdata-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).