Skip to content

Add server: SafetySearch #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Conversation

surabhya
Copy link

@surabhya surabhya commented Jun 22, 2025

This pull request adds the SafetySearch MCP server to the official registry. SafetySearch is a specialized server providing real-time access to FDA food safety data through 8 focused tools.

Motivation and Context

This change is needed to make a valuable, community-contributed server available to the broader MCP ecosystem. It solves the problem of difficult-to-access FDA food safety data by providing a simple, powerful, and well-documented set of tools for monitoring food recalls and adverse events.

How Has This Been Tested?

Yes, the SafetySearch server has been thoroughly tested.

  • It includes a comprehensive test suite (test_food_tools.py) that runs against the live FDA API endpoints.
  • All 8 tools are tested for various scenarios, including valid queries, edge cases (e.g., empty queries, non-existent products), and API error handling.
  • The tests are configured to run automatically with pytest and consistently pass.
  • The server has been run and validated locally, confirming that all tools return the expected detailed, structured output.

Breaking Changes

None. This is an additive change that introduces a new server to the registry and has no impact on existing servers or functionality.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

The SafetySearch server is designed to be a high-quality example of a production-ready, specialized MCP server. It features a dedicated API client, robust error handling, and provides detailed, user-friendly output for all its tools, going beyond simple data retrieval to offer analysis and safety insights. The codebase is clean, well-documented, and ready for public use.

@surabhya surabhya changed the title Add server: SafetySearc Add server: SafetySearch Jun 22, 2025
@tadasant
Copy link
Contributor

Server data is not stored in the registry repository here. You may submit your server to the README here instead: https://github.com/modelcontextprotocol/servers

@tadasant tadasant closed this Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants