Home / MCP registry index / io.github.pipeworx-io/fda-drug-competition
Fda Drug Competition
io.github.pipeworx-io/fda-drug-competition in the official MCP registry.
Endpoint https://gateway.pipeworx.io/fda-drug-competition/mcp. Source: github.com/pipeworx-io/mcp-fda-drug-competition.
The registry describes it as: Orange Book competitive intelligence from FDA's monthly official data ZIP.
We read its 59 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
ask_pipeworx ask_pipeworx_beta ask_pipeworx_grounded search_within deep_research discover_tools resolve_entity compare_entities subscribe unsubscribe list_subscriptions recent_alerts entity_profile recent_changes validate_claim company_facts company_register_search scan_dependency bet_research polymarket_arbitrage polymarket_edges polymarket_kalshi_spread polymarket_fill_risk polymarket_edge_tracker kalshi_weather_edge resolution_audit resolution_diff release_calendar_markets prediction_calibration archive_evidence archive_compare research_row classify_row pipeworx_trending suggest_questions generate_llms_txt ai_visibility_check scan_competitor_ai_presence pipeworx_feedback remember recall forget orange_book_product_search orange_book_competition_profile orange_book_application_detail orange_book_patent_expirations orange_book_exclusivity_expirations orange_book_loss_of_exclusivity_profile orange_book_generic_entry_timeline orange_book_reference_drug_landscape orange_book_expiry_cliff_calendar drug_patent_challenge_profile purple_book_product_search purple_book_competition_profile purple_book_biosimilars purple_book_interchangeables purple_book_reference_product purple_book_recent_changes purple_book_biosimilar_entry_timeline
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-pipeworx-io-fda-drug-competition)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.