Home / MCP registry index / ai.unquant/unquant
Unquant
ai.unquant/unquant in the official MCP registry.
Endpoint https://unquant.ai/mcp.
The registry describes it as: Financial data MCP for market, company, news, macro, and US Congress research.
We read its 28 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
ping datasets_list datasets_describe datasets_search catalog_list catalog_describe catalog_preview feedback_submit catalog_request market_price_history market_quote market_company_profile market_fundamentals market_symbol_search market_analyst_ratings market_earnings market_etf_holdings macro_calendar macro_indicator news_stock news_general news_impacts news_article macro_current_conditions politics_us_congress_trades politics_us_congress_aggregate account_request_upgrade account_upgrade_status
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-unquant-unquant)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.