FDA MCP Server
Related Servers
Alternatives to FDA MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceA ready-to-use starter implementation of the Model Context Protocol (MCP) server that enables applications to provide standardized context for LLMs with sample resources, tools, and prompts.23 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA deployable MCP server for Cloudflare Workers or Azure Functions that provides example tools (time, echo, math), prompt templates for code assistance, and configuration resources. Enables AI assistants to interact with edge-deployed services through the Model Context Protocol.-
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server template that enables running and experimenting with stdio and HTTP transports, and simulating AI agent interactions with custom tools such as deploys, git checks, API references, and status queries.3-

MCP Hackathon Serverofficial
AlicenseBqualityBmaintenanceProvides a template for building an MCP server with example tools, prompts, and resources, enabling developers to create a server that exposes data and actions to AI clients.19MIT- FlicenseBqualityDmaintenanceA starter template for building Model Context Protocol servers that can integrate AI assistants with custom tools, resource providers, and prompt templates.186 npm1-
- AlicenseBqualityDmaintenanceA template repository for building Model Context Protocol (MCP) servers that enable LLM clients to interact with custom tools and services through standardized JSON-RPC communication.3MIT
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusing it with another. However, the tool is a stub named 'example_search_datasets' and described as a placeholder, which reduces clarity about its actual purpose in the FDA domain.
There is only one tool, so no pattern can be established or violated. The name 'example_search_datasets' uses snake_case and follows a verb_noun structure, but the 'example_' prefix signals a placeholder rather than a production tool, which is a deviation from typical naming conventions.
A single tool is drastically insufficient for an FDA MCP server, which would be expected to cover drugs, foods, devices, recalls, adverse events, and more. One stub tool represents an extreme mismatch with the domain's scope.
The surface contains only a search stub with no detail retrieval, no list operations, no filters beyond a query string, and no other lifecycle operations. This is severely incomplete for any meaningful FDA data access.