recallpulse
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
recallpulse
How fast are complaints about a product piling up, and what does that velocity say about its recall risk? recallpulse is a local forwarding client for the hosted recall-risk MCP service: it answers tools/list locally from the captured tool definition and forwards every call to the service, returning the answers exactly as the service sends them back.
The single tool, recall_risk, returns a 0–100 risk score and band for a named product, brand or model, together with the signal inputs behind it — complaint velocity and acceleration, and the severe-hazard share. The score is a signal computed from public complaint data, shown with its inputs; it is not an official recall, not a claim that a product is defective, and not a verdict about any person. This client treats it that way: it forwards the question and passes the answer through.
The 1 captured tool is built; there are no omissions.
The tool
recall_risk— The complaint-velocity recall-risk signal for one tracked product, brand or model: a 0–100 risk score, its band, complaint velocity and acceleration, and the severe-hazard share.entityis required: a product/brand/model name or a tracked id (for exampleFord Mustang Mach-E,Dexcom G7, orveh-tesla-modely-2023).
Related MCP server: HouseCheck
Install and run
As an MCP server via npm:
npx -y @reneturcios/recallpulse mcpMCP client configuration:
{
"mcpServers": {
"recallpulse": {
"command": "npx",
"args": ["-y", "@reneturcios/recallpulse", "mcp"]
}
}
}As a container:
docker run -i ghcr.io/cloudcorprecords/recallpulse
docker run --rm ghcr.io/cloudcorprecords/recallpulse recall_risk '{"entity":"Dexcom G7"}'CLI
One binary serves both the command line and the MCP server. The tool is a subcommand taking a single JSON string with that tool's arguments:
recallpulse recall_risk '{"entity":"Ford Mustang Mach-E"}'
recallpulse recall_risk '{"entity":"veh-tesla-modely-2023"}'
recallpulse --versionExit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
RECALLRISK_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://cassandra.dropwatchhq.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with recallpulse error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from sourceThe test suite checks the served tool list against the captured surface (the 1 tool, deep-equal, with no title invented and required: [entity] exactly as captured), exercises the session handshake and its reuse, verifies that no Authorization header is ever sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Check a product's recall risk: score + active CPSC/FDA/NHTSA recalls for a product or brand.
Search product, food, drug, device and vehicle recalls, and watch your products and suppliers.
Is it recalled or fake? Recall lookup vs live US gov feeds + transparent counterfeit risk signal.
Match consumer products to official CPSC recalls and purchase source-linked evidence.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAccess US consumer-product safety recalls from the CPSC, free and without authentication.84 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables determining whether a specific product unit is affected by FDA/CPSC recalls by evaluating the unit's lot, date, and other codes against frozen recall notices, returning affected, not affected, or needed-code questions.MIT
- AlicenseAqualityBmaintenanceSearches US product recalls across CPSC, FDA, and NHTSA in one call, matching by name, brand, model number, UPC, or VIN with confidence scoring.31MIT
- AlicenseNot gradedqualityBmaintenanceEnables Alexa+ and any MCP client to ask out loud whether a car, crib, food or medicine has been recalled, drawing on NHTSA, CPSC and FDA data in parallel. Returns a short spoken answer plus structured recall details such as hazard, remedy and official link.MIT