Skip to main content
Glama

Server Details

FDA inspection outcomes, Form 483 observations, compliance actions and import refusals for drug…

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.2% over 21 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-fda-inspections
GitHub Stars
0
Server Listing
fda-inspections

TDQS

A3.9/5.0

Scored across 41 tools

Disambiguation3/5

Many tools overlap heavily around universal lookup and research: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, company_facts, entity_profile, compare_entities, and recent_changes all serve related 'get information about X' needs. The descriptions do provide strong usage guidance, so an agent can often choose correctly, but the boundaries are not cleanly distinct.

Naming Consistency4/5

Nearly every tool uses snake_case, with clear prefixes for domains such as fda_, polymarket_, and pipeworx_. The main deviation is that some names are verb_noun while others are noun_phrases or adjective_noun, so the pattern is not strictly verb_noun throughout.

Tool Count2/5

At 41 tools, the server is well over the 25-tool threshold that typically signals an oversized surface. While each tool may earn its place in a universal data gateway, the count is high enough to burden tool selection and context.

Completeness4/5

The surface covers a broad range of data-access workflows: routing, grounded answers, deep research, entity resolution, financial facts, comparisons, memory, subscriptions, alerts, and specialist FDA/Pipeworx packs. Some domain-specific operations are only reachable indirectly through meta-tools, but the core lifecycle and major gaps are largely addressed.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 41 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedfda_483_citations
    • First observedfda_compliance_actions
    • First observedfda_firm_risk_profile
    • First observedfda_import_refusals
    • First observedfda_inspections
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.