Home / MCP registry index / io.github.pipeworx-io/fda-devices
Fda Devices
io.github.pipeworx-io/fda-devices in the official MCP registry.
Endpoint https://gateway.pipeworx.io/fda-devices/mcp. Source: github.com/pipeworx-io/mcp-fda-devices.
The registry describes it as: FDA medical-device regulatory intelligence from keyless openFDA datasets.
We read its 53 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 fda_device_510k_search fda_device_510k_summary fda_device_pma_search fda_device_recalls fda_device_adverse_events fda_device_event_counts fda_device_company_profile fda_device_classification fda_device_udi_search fda_device_establishment_search fda_device_product_code_profile
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-devices)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.
Related
| ch.swisslivingindex/swiss-living-index ch.swisslivingindex/swiss-living-index | 72 tools, nothing matched 2026-10-26 |
| Framezone app.framezone/framezone | 50 tools, nothing matched 2026-10-22 |
| Medical Codes io.github.pipeworx-io/medical-codes | 47 tools, nothing matched 2026-10-26 |
| Nice Guidance io.github.pipeworx-io/nice-guidance | 47 tools, nothing matched 2026-10-27 |
| Nihr io.github.pipeworx-io/nihr | 47 tools, nothing matched 2026-10-27 |
| Myhealthfinder io.github.pipeworx-io/myhealthfinder | 46 tools, nothing matched 2026-10-27 |