DeepRecall - Product Safety Intelligence
REMOTE · MCP.DEEPRECALL.IO
Search 120,000+ recalled products from 8 global safety agencies using AI similarity.
Available components
Last scanned (17 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 556 tokens (~185/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 +58
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 27 Oct 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 0
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.deeprecall.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.deeprecall.io | CN=WE1,O=Google Trust Services,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | e1e66af546dad8ec131856ec2526c45d |
| SANs: mcp.deeprecall.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.deeprecall.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| deeprecall.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.deeprecall.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.deeprecall.io/mcp | HTTPS enforced | 301 | https://mcp.deeprecall.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_data_sources ~60
Get information about available recall data sources. Returns a list of all supported regulatory agencies and their coverage. This is a free call that does not consume API credits. Returns: Dictionary with data sources and their descriptions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_recalls ~457
Search for recalled products similar to your query. This tool searches DeepRecall's global product safety database using AI-powered multimodal matching. Provide a text description and/or product images to find similar recalled products. Use Cases: - Pre-purchase safety checks: Before buying, verify if similar products were recalled - Supplier vetting: Check if a supplier's products have safety issues - Marketplace compliance: Verify products against recall databases - Consumer protection: Identify potentially hazardous products Data Sources: - us_cpsc: US Consumer Product Safety Commission - us_fda: US Food and Drug Administration - safety_gate: EU Safety Gate (Europe) - uk_opss: UK Office for Product Safety & Standards - canada_recalls: Health Canada Recalls - oecd: OECD GlobalRecalls portal - rappel_conso: French Consumer Recalls - accc_recalls: Australian Competition and Consumer Commission Cost: 1 API credit per search Args: content_description: Text description of the product (e.g., "children's toy with small parts") image_urls: List of product image URLs for visual matching (1-10 images) filter_by_data_sources: Limit search to specific agencies (optional) top_k: Number of results (1-100, default: 10) model_name: Fusion model - fuse_max (recommended), fuse_flex, or fuse input_weights: Weights for [text, images], must sum to 1.0 api_key: Your DeepRecall API key (optional if provided via X-API-Key header) Returns: Search results with matched recalls, scores, and product details Example: search_recalls( content_description="baby crib with drop-side rails", top_k=5 )
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| content_description | – | – | – |
| filter_by_data_sources | – | – | – |
| image_urls | – | – | – |
| input_weights | array | – | – |
| model_name | string | – | – |
| top_k | integer | – | – |
No output schema declared.
No examples provided.
How do I install the DeepRecall - Product Safety Intelligence MCP server?
DeepRecall - Product Safety Intelligence is a hosted endpoint at https://mcp.deeprecall.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.deeprecall.io
claude mcp add --transport http adrida-deeprecall-mcp 'https://mcp.deeprecall.io/mcp'
What is the DeepRecall - Product Safety Intelligence MCP server?
DeepRecall - Product Safety Intelligence is an MCP server listed in the public MCP registry as io.github.adrida/deeprecall-mcp. Search 120,000+ recalled products from 8 global safety agencies using AI similarity. This page covers its hosted endpoint (https://mcp.deeprecall.io/mcp).
Is the DeepRecall - Product Safety Intelligence MCP server safe to use?
DeepRecall - Product Safety Intelligence scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DeepRecall - Product Safety Intelligence MCP server expose?
DeepRecall - Product Safety Intelligence exposes 2 tools: search_recalls, get_data_sources. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Does the DeepRecall - Product Safety Intelligence MCP server require authentication?
No. We connected to DeepRecall - Product Safety Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DeepRecall - Product Safety Intelligence MCP server still maintained?
DeepRecall - Product Safety Intelligence is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the DeepRecall - Product Safety Intelligence MCP server?
VerifyMCP ran 12 checks on DeepRecall - Product Safety Intelligence, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about DeepRecall - Product Safety Intelligence: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.