Home / MCP registry index / com.siliconfloor/silicon-floor
Silicon Floor
com.siliconfloor/silicon-floor in the official MCP registry.
Endpoint https://siliconfloor.com/mcp. Source: github.com/Baptoshi/silicon-floor.
The registry describes it as: Terminal for AI agents on AI & chip stocks: who owns, buys, sells — every figure from SEC filings.
We read its 19 tools on 2026-10-21. 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
list_companies get_company compare_companies screen_companies get_ownership get_filings get_dividends get_signals get_news what_changed get_market_overview get_market get_holders get_relationships get_insider_trading get_fund_flows get_financials get_figure_history get_price_history
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-siliconfloor-silicon-floor)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.