Consumer Product Recall Evidence
REMOTE · EXPERIMENT-008-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 22
Match consumer products to official CPSC recalls and purchase source-linked evidence.
Available components
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 138 tokens (~46/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Consumer Product Recall Evidence MCP server?
Consumer Product Recall Evidence is a hosted endpoint at https://experiment-008-production.up.railway.app/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 · experiment-008-production.up.railway.app
claude mcp add --transport http thryvebaseline-agent-services-008 'https://experiment-008-production.up.railway.app/mcp'
{
"mcpServers": {
"thryvebaseline-agent-services-008": {
"url": "https://experiment-008-production.up.railway.app/mcp"
}
}
} {
"servers": {
"thryvebaseline-agent-services-008": {
"type": "http",
"url": "https://experiment-008-production.up.railway.app/mcp"
}
}
} [mcp_servers.thryvebaseline-agent-services-008] url = "https://experiment-008-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thryvebaseline-agent-services-008": {
"type": "remote",
"url": "https://experiment-008-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add thryvebaseline-agent-services-008 --url 'https://experiment-008-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
thryvebaseline-agent-services-008:
url: "https://experiment-008-production.up.railway.app/mcp" {
"McpServers": {
"thryvebaseline-agent-services-008": {
"Transport": "http",
"Url": "https://experiment-008-production.up.railway.app/mcp"
}
}
} assistant mcp add thryvebaseline-agent-services-008 -t streamable-http -u 'https://experiment-008-production.up.railway.app/mcp'
{
"mcpServers": {
"thryvebaseline-agent-services-008": {
"type": "http",
"url": "https://experiment-008-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://experiment-008-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of experiment-008-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 400 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://experiment-008-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://experiment-008-production.up.railway.app/mcp | HTTPS enforced | 301 | https://experiment-008-production.up.railway.app/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 →
build_product_recall_evidence ~46
Purchase a $0.20 CPSC hazard/remedy evidence package; no individual-unit remedy completion or broader safety conclusion is made.
| Name | Type | Req | Description |
|---|---|---|---|
| product_token | string | yes | – |
No output schema declared.
No examples provided.
match_product_recall ~33
Purchase a $0.03 exact CPSC recall-notice match result.
| Name | Type | Req | Description |
|---|---|---|---|
| product_token | string | yes | – |
No output schema declared.
No examples provided.
resolve_consumer_product ~59
Free: conservatively match an exact model to a published CPSC recall notice; absence is not proof of safety or no recall.
| Name | Type | Req | Description |
|---|---|---|---|
| manufacturer | string|null | – | – |
| model | string | yes | – |
| product_name | string | yes | – |
No output schema declared.
No examples provided.
What is the Consumer Product Recall Evidence MCP server?
Consumer Product Recall Evidence is an MCP server listed in the public MCP registry as io.github.ThryveBaseline/agent-services-008. Match consumer products to official CPSC recalls and purchase source-linked evidence. This page covers its hosted endpoint (https://experiment-008-production.up.railway.app/mcp).
Is the Consumer Product Recall Evidence MCP server safe to use?
Consumer Product Recall Evidence scores 68 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 Consumer Product Recall Evidence MCP server expose?
Consumer Product Recall Evidence exposes 3 tools: resolve_consumer_product, match_product_recall, build_product_recall_evidence. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.
Does the Consumer Product Recall Evidence MCP server require authentication?
Its publisher declares no required credentials for Consumer Product Recall Evidence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Consumer Product Recall Evidence MCP server still maintained?
Consumer Product Recall Evidence is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.