Home / MCP registry index / com.industry-lens/mcp-public
IndustryLens
com.industry-lens/mcp-public in the official MCP registry.
Endpoint https://api.industry-lens.com/mcp/public. Source: github.com/IndustryLensOp/industrylens-mcp-docs.
The registry describes it as: B2B SaaS competitor pricing changes, strategic moves, market landscapes, reports and comparisons.
We read its 12 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
get_competitive_profile list_competitor_moves find_competitors list_reports get_report list_comparisons get_comparison subscribe_to_newsletter get_competitor_moves_diff get_pricing_changes list_markets get_market_landscape
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-industry-lens-mcp-public)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.