Proposal: a tennis MCP server for the daily-sports slice of the universe
Addressed to the operator, per your own note that Phil doesn't read issues.
Since "daily sports" is in Phil's Polymarket universe and every cycle settles yesterday's positions against official resolutions, a tennis data tool might earn its keep twice: fixtures and H2H for pre-match research, and live/final match state for settlement verification.
Disclosure: I run the Live Tennis API. We host an MCP endpoint at mcp.livetennisapi.com — fixtures, H2H, rankings, live scores as MCP tools, so wiring it is config, not code. The free tier is keyed, 30 req/min / 100 req/day (live scores, players, fixtures, usage), which fits an hourly-cycle budget; completed-match history is a paid tier, and WebSocket plus model win probability are top tier — Phil wouldn't need those for research + settlement checks.
Strictly an issue, deliberately: sensing and tooling are the agent's own working tree, so this is a suggestion for the operator to wire (or hand to Phil via journal/operator-notes.md), not a PR. If tennis isn't an edge class you want Phil spending cycles on, close this — entirely fair.
Proposal: a tennis MCP server for the daily-sports slice of the universe
Addressed to the operator, per your own note that Phil doesn't read issues.
Since "daily sports" is in Phil's Polymarket universe and every cycle settles yesterday's positions against official resolutions, a tennis data tool might earn its keep twice: fixtures and H2H for pre-match research, and live/final match state for settlement verification.
Disclosure: I run the Live Tennis API. We host an MCP endpoint at mcp.livetennisapi.com — fixtures, H2H, rankings, live scores as MCP tools, so wiring it is config, not code. The free tier is keyed, 30 req/min / 100 req/day (live scores, players, fixtures, usage), which fits an hourly-cycle budget; completed-match history is a paid tier, and WebSocket plus model win probability are top tier — Phil wouldn't need those for research + settlement checks.
Strictly an issue, deliberately: sensing and tooling are the agent's own working tree, so this is a suggestion for the operator to wire (or hand to Phil via
journal/operator-notes.md), not a PR. If tennis isn't an edge class you want Phil spending cycles on, close this — entirely fair.