Skip to main content
Glama
Sign In
recall-check-mcp

recall-check-mcp

by arhancanli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to recall-check-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-cpsc

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Access US consumer-product safety recalls from the CPSC, free and without authentication.
      319 npm
      MIT

    • Recall Radar

      theluckystrike
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • HouseCheck

      dud8
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct query mode: recent_recalls is temporal/agency browsing, check_recalls is product-name/UPC search across CPSC/FDA, and vehicle_recalls is VIN/make-model lookup for NHTSA. Though recent_recalls and check_recalls both cover CPSC/FDA, one is a listing by date and the other is a targeted search, so agents should not confuse them.

    Naming Consistency4/5

    All names follow the same _recalls suffix and snake_case convention, with descriptive prefixes: recent, check, vehicle. This is not a strict verb_noun pattern throughout, but the pattern is predictable and readable enough that agents can infer each tool's scope from its name.

    Tool Count5/5

    Three tools is a well-scoped set for a recall-checking server: one for browsing recent recalls, one for product search, and one for vehicle-specific recalls. Each tool serves a distinct and necessary purpose with no redundancy or filler.

    Completeness4/5

    The tool surface covers the primary recall workflows: recent recalls, product recall search, and vehicle recalls by VIN or vehicle attributes. Minor gaps exist, such as no direct recall-detail lookup by recall ID and no single unified search across CPSC, FDA, and NHTSA, but agents can work around these by combining the available tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources