A
license-
qualityC
maintenanceAccess US consumer-product safety recalls from the CPSC, free and without authentication.
9
MIT
recall-risk
Server Details
Check a product's recall risk: score + active CPSC/FDA/NHTSA recalls for a product or brand.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 4.4/5 across 1 of 1 tools scored.
Server CoherenceB
Disambiguation5/5
With only one tool, there is no possibility of ambiguity between tools.
Naming Consistency5/5
The single tool name 'recall_risk' follows a clear verb_noun pattern, consistent with best practices.
Tool Count1/5
A server intended to provide recall risk signals would typically need multiple tools for different endpoints (e.g., list products, get historical trends). One tool is far too few for a meaningful service.
Completeness1/5
The tool surface is severely incomplete: only one operation is provided, lacking risk search, product listing, historical data, or any complementary functionality needed for a recall risk domain.
Available Tools
1 toolrecall_riskAInspect
Get the current complaint-velocity recall-risk signal for a tracked product/brand/model. Returns a 0-100 risk score, band, complaint velocity & acceleration, and severe-hazard share. This is a RISK SIGNAL from public complaint data, NOT an official recall or a claim the product is defective.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entity | Yes | Product/brand/model name or tracked id (e.g. 'Ford Mustang Mach-E', 'Dexcom G7', 'veh-tesla-modely-2023'). |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the return values (0-100 risk score, band, complaint velocity, acceleration, severe-hazard share) and explicitly states it is not an official recall. With no annotations provided, the description appropriately carries the burden of transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences totaling 33 words, front-loaded with purpose, and every sentence adds value—no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple parameter set (one required string), no output schema, and no sibling tools, the description is complete: it explains what the tool does, what it returns, and includes a necessary caveat.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'entity' has a schema description, and the tool description provides examples (e.g., 'Ford Mustang Mach-E', 'Dexcom G7', 'veh-tesla-modely-2023'), adding meaningful context beyond the schema alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'recall-risk signal for a tracked product/brand/model'. It distinguishes itself from an official recall by warning it is a risk signal from public complaint data, not an actual recall.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance is given. There are no sibling tools to differentiate from, but the description implies usage for obtaining a risk signal. No prerequisites (e.g., product must be tracked) are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
deeprecall-mcpofficial
Alicense-qualityDmaintenanceSearch 120,000+ recalled products from CPSC, FDA, EU Safety Gate, and other global agencies via MCP. Enables AI agents to check product safety by text or image.Apache 2.0- Alicense-qualityCmaintenanceEnables instant U.S. vehicle recall lookup by make, model, and year using official NHTSA data.MIT