Home / MCP registry index / com.voxodds/voxodds
com.voxodds/voxodds
com.voxodds/voxodds in the official MCP registry.
Endpoint https://voxodds.com/mcp. Source: github.com/softdevfz/voxodds-mcp.
The registry describes it as: All-in outcome rankings with live depth, fees, verified rules, EV checks, and track records.
We read its 18 tools on 2026-10-22. 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
submit_forecast get_market_odds get_executable_quote compare_executable_quotes list_executable_opportunities list_arbitrage_candidates list_sportsbook_surebets get_world_cup_odds get_world_cup_brief get_world_cup_matchday list_trending_markets check_bet find_best_price compare_platforms get_edge_signals get_track_record get_forecaster_record get_research_theses
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-voxodds-voxodds)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.