RecallLens
REMOTE · RECALLS.TRYSTARRYNIGHTOPS.COM
US recall lookup: NHTSA vehicle and VIN recalls, FDA food, drug and device recalls, CPSC products.
Available components
Last scanned (18 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1303 tokens (~260/item across 5 items; 5 tools + 0 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Authorization
- 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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 20 Nov 26 +1
- Server version: 1.0.11 → 1.0.12 functional
- Server version: 1.0.10 → 1.0.11 functional
- 19 Nov 26 0
- Server version: 1.0.9 → 1.0.10 functional
- Server version: 1.0.8 → 1.0.9 functional
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Server version: 1.0.7 → 1.0.8 functional
- Server version: 1.0.6 → 1.0.7 functional
- 16 Nov 26 +1
- Server version: 1.0.5 → 1.0.6 functional
- 15 Nov 26 0
- Server version: 1.0.4 → 1.0.5 functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Server version: 1.0.3 → 1.0.4 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://recalls.trystarrynightops.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trystarrynightops.com | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | bd45dfe03e7d05060e78a0b64a2fe9dd |
| SANs: trystarrynightops.com, recalls.trystarrynightops.com, *.recalls.trystarrynightops.com | ||||||
| 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 recalls.trystarrynightops.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| trystarrynightops.com. | 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://recalls.trystarrynightops.com/mcp | Verified | 200 | |
| http (plaintext) | http://recalls.trystarrynightops.com/mcp | Inconclusive | 405 |
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 →
consumer_product_recalls CPSC consumer product recalls ~288
Searches US Consumer Product Safety Commission (CPSC) recalls of consumer products such as toys, cribs, strollers, furniture, heaters, e-bikes, batteries and appliances, newest first. Keywords (every word must appear) are matched against the recall title, product names, models and types, description, hazard, firm and retailer names, and UPCs; a CPSC recall number also works. Optional recall-date range. Returns recall number, date, title, products, units, hazard, remedy and the cpsc.gov link. Does not cover vehicles, food, drugs, cosmetics or medical devices.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Earliest recall date, YYYY-MM-DD. |
| date_to | string | – | Latest recall date, YYYY-MM-DD. |
| detail | string | – | "brief" (default) keeps each result short; "full" adds the complete text fields. |
| limit | integer | – | Results per page (1-10, default 10; at most 5 with detail "full"). |
| offset | integer | – | Number of results to skip, for paging (0-200). |
| query | string | – | Keywords, e.g. "space heater", "IKEA dresser", "magnet", a model number, a UPC or a recall number like 27054. Up to 6 words. Optional if a date range is given. |
No output schema declared.
No examples provided.
food_drug_device_recalls FDA food, drug and device recalls ~356
Searches FDA recall enforcement reports published through openFDA for food, drugs and medical devices, newest report date first. Optional filters: keywords (every word must appear in the product description, reason for recall, recalling firm or lot/code information; "quoted phrases" are kept together), product type, classification (Class I, II or III), status and report-date range. Returns recall number, class, status, firm, product, reason, distribution, dates and a link to the openFDA record. The data is FDA's weekly Enforcement Report (2012 onward), which can lag FDA's recall announcements.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | – | FDA recall class. Class I is the most serious. |
| date_from | string | – | Earliest Enforcement Report date, YYYY-MM-DD. |
| date_to | string | – | Latest Enforcement Report date, YYYY-MM-DD. |
| detail | string | – | "brief" (default) keeps each result short; "full" adds the complete text fields. |
| limit | integer | – | Results per page (1-25, default 10). At most 10 without product_type or for devices, and at most 5 with detail "full". |
| offset | integer | – | Number of results to skip, for paging (0-100). Without product_type, offset + limit can be at most 20. |
| product_type | string | – | Limit to one FDA product type. Omit to search all three. |
| query | string | – | Keywords, e.g. "peanut butter", "listeria", "insulin pen", a firm name or a lot number. Up to 6 words. Optional. |
| status | string | – | Recall status in the Enforcement Report. |
No output schema declared.
No examples provided.
vehicle_recall_campaign NHTSA recall campaign details ~180
Returns one NHTSA recall campaign by its campaign number (e.g. 20V314000, 20V-314 or 23C001): manufacturer, report date, component, summary, consequence, remedy, potential number of units affected, advisories, and the makes, models and model years it covers. Works for vehicle (V), equipment (E), tire (T) and child seat (C) campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_number | string | yes | NHTSA campaign number, e.g. "20V314000", "20V-314" or "23C001". |
| detail | string | – | "brief" (default) keeps each result short; "full" adds the complete text fields. |
| limit | integer | – | Maximum number of make/model entries to list (1-200, default 40). |
No output schema declared.
No examples provided.
vehicle_recalls Vehicle recalls by make, model and year ~257
Lists NHTSA safety recall campaigns for a US-market vehicle by make, model and model year, newest first: campaign number, report date, component, a short defect summary, the safety risk, the remedy, any "do not drive" or "park outside" advisory, and a link to the NHTSA recall page. If the model name does not match NHTSA's naming, it returns the closest NHTSA model names for that make and year. It covers campaigns issued for the model, not whether a specific vehicle has been repaired.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "brief" (default) keeps each result short; "full" adds the complete text fields. |
| limit | integer | – | Maximum number of campaigns to return (1-50, default 10). |
| make | string | yes | Vehicle make, e.g. "Honda", "Chevrolet", "Ford". Short forms such as "Chevy" and "VW" are accepted. |
| model | string | yes | Model name, e.g. "Accord", "F-150", "Silverado 1500", "Model 3". |
| model_year | integer | yes | Four-digit model year, e.g. 2018. |
No output schema declared.
No examples provided.
vin_recalls Vehicle recalls by VIN ~222
Checks a 17-character vehicle identification number (VIN): validates its check digit, decodes make, model and model year with NHTSA's vPIC service (only the first 11 characters are sent, or 14 for low-volume manufacturers; never the serial number), then lists the NHTSA safety recall campaigns issued for that make, model and year, with the same fields as vehicle_recalls. It does not confirm whether this specific vehicle is included in a campaign or has been repaired; NHTSA's own VIN lookup at nhtsa.gov/recalls is the official source for that.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "brief" (default) keeps each result short; "full" adds the complete text fields. |
| limit | integer | – | Maximum number of campaigns to return (1-50, default 10). |
| vin | string | yes | 17-character VIN, e.g. "1HGCV1F37JA000001". Spaces and dashes are ignored; letters I, O and Q never occur in VINs. |
No output schema declared.
No examples provided.
How do I install the RecallLens MCP server?
RecallLens is a hosted endpoint at https://recalls.trystarrynightops.com/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 · recalls.trystarrynightops.com
claude mcp add --transport http com-trystarrynightops-recalllens 'https://recalls.trystarrynightops.com/mcp'
What is the RecallLens MCP server?
RecallLens is an MCP server listed in the public MCP registry as com.trystarrynightops/recalllens. US recall lookup: NHTSA vehicle and VIN recalls, FDA food, drug and device recalls, CPSC products. This page covers its hosted endpoint (https://recalls.trystarrynightops.com/mcp).
Is the RecallLens MCP server safe to use?
RecallLens scores 70 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 RecallLens MCP server expose?
RecallLens exposes 5 tools: vehicle_recalls, vin_recalls, vehicle_recall_campaign, food_drug_device_recalls, consumer_product_recalls. Their descriptions and schemas cost roughly 1,303 tokens of context every time the server is loaded.
Does the RecallLens MCP server require authentication?
No. We connected to RecallLens without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RecallLens MCP server still maintained?
RecallLens 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 RecallLens MCP server?
VerifyMCP ran 12 checks on RecallLens, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about RecallLens: HTTPS. 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.