Read-only Polymarket sports and esports data: wallet grades on settled P&L, large trades, markets.
The official Agent Plugin for 0xinsider - Polymarket analytics for sports and esports in real-time.
It bundles the 0xinsider MCP server with five skills that teach an agent how to read large trades, wallet grades, sharp-money flow, and published research without misreporting them.
npx skills add 0xinsider/agent-plugin
Or install one skill without adding the whole plugin:
npx skills use 0xinsider/agent-plugin@0xinsider-api-access
| Skill | Covers |
|---|---|
0xinsider-api-access | Credentials, sandbox vs live hosts, MCP transports, rate limits, typed errors |
polymarket-whale-trades | Large-trade feed, history replay, counterparties, significance score |
polymarket-wallet-grades | Trader grades, settled P&L and its trust metadata, leaderboards, position timelines |
polymarket-sharp-money | Directional flow, market intel, sports-edge signals, Insider Radar flags |
polymarket-market-research | Market search and explore, published research, report snapshots |
AGENTS.md holds the rules for AI coding agents writing
integration code against the API. .cursorrules mirrors it.
mcp.json points at the remote Streamable HTTP endpoint:
{
"mcpServers": {
"0xinsider": {
"type": "http",
"url": "https://0xinsider.com/mcp",
"headers": { "Authorization": "Bearer ${OXINSIDER_API_KEY}" }
}
}
}
The server exposes 33 tools across traders, markets, large trades, positions,
flow, research, reports, and webhooks. Its card is at
/.well-known/mcp.
A local stdio path ships in the CLI:
npx -y 0xinsider init
Every documented operation answers from the sandbox with no credential:
curl -s https://0xinsider.com/sandbox/api/v1/leaderboard
One POST returns a sandbox key and the steps to live access:
curl -s -X POST https://api.0xinsider.com/api/v1/agents/register \
-H 'Content-Type: application/json' -d '{"name":"my-agent"}'
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @0xinsider/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-0xinsider-mcp": {
"command": "npx",
"args": [
"-y",
"@0xinsider/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference0xinsider works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.