Home / MCP registry index / io.github.0xinsider/mcp

0xinsider

io.github.0xinsider/mcp in the official MCP registry. Endpoint https://api.0xinsider.com/api/v1/mcp. Source: github.com/0xinsider/agent-plugin.

The registry describes it as: Read-only Polymarket sports and esports data: wallet grades on settled P&L, large trades, markets.

We read its 55 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_leaderboard get_trader batch_get_traders get_large_trades get_large_trade get_large_trades_history get_whale_trades get_whale_trade get_whale_trades_history get_edge_hunter list_games get_game get_market_flow batch_get_market_flow get_market_intel batch_get_market_intel get_sharp_money_flows get_smart_money_flows get_market_snapshot get_suspicious_trades get_suspicious_trade get_insider_radar get_insider_radar_flag get_positions get_position_timeline get_position_timeline_by_id search_markets search_content explore_markets get_event_replay_since list_webhooks get_webhook get_daily_report_snapshot get_weekly_report_snapshot get_monthly_report_snapshot get_report get_trader_export_snapshot get_coverage get_platforms get_large_positions get_trending_wallets get_trader_pnl get_pick_of_the_day get_pick_of_the_day_ledger_entry get_pick_of_the_day_archive get_trader_context get_trader_categories get_trader_grade_at get_market_holders get_market_candles get_combo_fills get_combos_summary get_combo get_large_trade_counterparty_executions get_large_trade_counterparty_makers

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-0xinsider-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-0xinsider-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26