Home / MCP registry index / io.helious/market-intelligence
Helious market intelligence
io.helious/market-intelligence in the official MCP registry.
Endpoint https://helious.io/mcp.
The registry describes it as: US Treasury auction tails, the live curve regime, scored macro releases, and why rates moved.
We read its 25 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
get_rates_and_curve get_curve_history get_fx_board get_vol_board get_inflation get_jobs get_rate_path get_treasury_issuance get_correlations get_hormuz_transits get_yield_closes get_economic_calendar list_series get_series get_auctions get_feed get_document_digests get_fed_roster get_squawk_sessions get_access_info get_treasury_curve get_nasdaq100 get_rate_odds get_market_context get_earnings
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-helious-market-intelligence)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.