Consumer Product Recall Evidence

io.github.ThryveBaselinePublished by GitHub account ThryveBaselinev0.1.0Updated Oct 24, 2026

Match consumer products to official CPSC recalls and purchase source-linked evidence.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Matches consumer products to official CPSC recall records and purchase-source-linked evidence.

What you can do
This remote MCP server lets an assistant look up consumer products against official CPSC recall information and connect them to purchase-source-linked evidence. The registry description states it matches consumer products to official CPSC recalls and purchase source-linked evidence. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs to check whether a consumer product has an official CPSC recall, or to tie a product to evidence about where it was purchased. Less useful for general product research or non-recall questions.
Requirements
A remote streamable HTTP endpoint at the provider's URL; no packages, environment variables, headers, or authentication are declared. Network access to that endpoint is required.
Before you install
The manifest declares no authentication, so anyone with the endpoint can reach it; avoid sending personal or purchase data you would not want exposed. Recall and evidence results come from a third party and should be verified against official CPSC sources before acting.

Installation

In SourceWeft

  1. Open Consumer Product Recall Evidence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ThryveBaseline%2Fagent-services-008/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "consumer-product-recall-evidence": {
      "type": "http",
      "url": "https://experiment-008-production.up.railway.app/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.