Home / MCP registry index / com.folionomiq/folionomiq
Folionomiq
com.folionomiq/folionomiq in the official MCP registry.
Endpoint https://folionomiq.com/mcp.
The registry describes it as: Measures a portfolio from price history: independent bets, what funds own, past crises. No advice.
We read its 22 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
measure_portfolio compare_portfolios test_a_change search_symbols validate_symbols portfolio_structure look_through past_crises portfolio_report factor_exposure currency_effect health_axes sweep_holding reverse_stress return_history plain_findings last_price asset_info monthly_plan walk_forward check_before_you_buy living_off_it
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-folionomiq-folionomiq)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.