_ registry / mcp http-sse · checked 9m ago

nhtsa-vehicle-safety-mcp-server

https://nhtsa.caseyjhand.com

Registry code: 276f606b0b584eca

api record

Use the nhtsa_* tools for U.S. vehicle safety data: recalls, complaints, NCAP crash ratings, defect investigations, and VIN decoding. nhtsa_get_vehicle_safety is the default for general 'is this car safe?' questions; nhtsa_lookup_vehicles confirms make/model spelling first.

endpoint
https://nhtsa.caseyjhand.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is nhtsa-vehicle-safety-mcp-server live?
Yes — it answered the hub's last check (checked 9m ago). It answered 99% of checks over the last 30 days.
Is nhtsa-vehicle-safety-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does nhtsa-vehicle-safety-mcp-server have?
7 tools: nhtsa_search_complaints, nhtsa_get_safety_ratings, nhtsa_decode_vin, nhtsa_get_vehicle_safety, nhtsa_lookup_vehicles, nhtsa_search_recalls, nhtsa_search_investigations.
Is nhtsa-vehicle-safety-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.3%· all time 99.3%

latency
820ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 587 checks · signed record
  • down → live
  • degraded → down· HTTP 530
  • live → degraded· HTTP 530
  • degraded → live
_ what it is for
topic
iot & hardware vehicles & automotive
used for
  • check a vehicle for safety recalls
  • decode a vin
  • get crash test ratings
  • search vehicle safety complaints
takes → gives
text → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
1 open 6 never probed 1 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • nhtsa_search_investigations reads open 12h ago

    Search NHTSA defect investigations from the ODI flat file — covering Preliminary Evaluations (PE), Engineering Analyses (EA), Defect Petitions (DP), Recall Queries (RQ), Audit Queries (AQ), and additional ODI types. make, model, and component are structured filters against the investigation record's vehicle associations. All filters are ANDed. Use nhtsaId to fetch one investigation by its exact ID — including the investigationId nhtsa_search_recalls returns for a campaign. Investigations may link to a resulting recall campaign via recallCampaign.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "make": {
      "type": "string",
      "description": "Structured filter — matches against the investigation's associated vehicle makes (e.g., \"TOYOTA\"). ANDed with other filters."
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Max investigations to return. Defaults to 20; max 25. The cap is lower than the other paginated tools because a single investigation summary can run several thousand characters and is rendered in full."
    },
    "model": {
      "type": "string",
      "description": "Structured filter — matches against the investigation's associated vehicle models. ANDed with other filters."
    },
    "query": {
      "type": "string",
      "description": "Free-text search across investigation ID, subject, and summary."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Pagination offset into the matching investigations. Defaults to 0."
    },
    "status": {
      "enum": [
        "O",
        "C"
      ],
      "type": "string",
      "description": "Filter by status: \"O\" (Open) or \"C\" (Closed). Omit to include both."
    },
    "nhtsaId": {
      "type": "string",
      "description": "Exact NHTSA investigation ID (e.g. \"EA23003\"), case-insensitive. Fetches that one record — mutually exclusive with every other filter."
    },
    "component": {
      "type": "string",
      "description": "Structured filter — matches against the investigation's affected components (e.g., \"STEERING\"). ANDed with other filters."
    },
    "investigationType": {
      "type": "string",
      "description": "Filter by ODI investigation type code (the leading letters of the NHTSA ID). Named types: \"PE\" (Preliminary Evaluation), \"EA\" (Engineering Analysis), \"DP\" (Defect Petition), \"RQ\" (Recall Query), \"AQ\" (Audit Query). Additional valid codes present in the dataset: \"SQ\", \"EQ\", \"RP\", \"ID\", \"TA\", \"C\". Pass any code exactly as it appears in the investigation ID prefix."
    }
  },
  "additionalProperties": false
}
    arguments 51 lines
  • nhtsa_search_complaints reads unknown 21h ago

    Search consumer safety complaints filed with NHTSA for a specific vehicle. Returns a component breakdown over all matching complaints plus a paginated slice of the most recent complaints. Use for common problems, failure patterns, or owner-reported issues.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "make",
    "model",
    "modelYear"
  ],
  "properties": {
    "make": {
      "type": "string",
      "description": "Vehicle manufacturer."
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max complaint narratives to return. Defaults to 20; max 50. componentBreakdown always reflects all matching complaints."
    },
    "model": {
      "type": "string",
      "description": "Vehicle model."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Pagination offset into the filing-date-descending complaint list. Defaults to 0. componentBreakdown is unaffected by pagination."
    },
    "component": {
      "type": "string",
      "description": "Filter to a specific component (uppercase, e.g., \"ENGINE\", \"AIR BAGS\", \"ELECTRICAL SYSTEM\"). Matches within comma-separated component lists. Omit to see all."
    },
    "modelYear": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Model year, a whole number."
    }
  },
  "additionalProperties": false
}
    arguments 42 lines
  • nhtsa_get_safety_ratings reads unknown 12h ago

    Get NCAP crash test ratings and ADAS feature availability for a vehicle. Use when the user specifically wants crash test stars, rollover risk, or wants to compare safety features across vehicles. NCAP data available from 1990+, best coverage for 2011+.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "make": {
      "type": "string",
      "description": "Vehicle manufacturer. Required with model and modelYear when vehicleId is omitted."
    },
    "model": {
      "type": "string",
      "description": "Vehicle model. Required with make and modelYear when vehicleId is omitted."
    },
    "modelYear": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Model year, a whole number. Required with make and model when vehicleId is omitted. NCAP coverage increases significantly for 2011+."
    },
    "vehicleId": {
      "type": "number",
      "description": "Specific NCAP vehicle ID (from prior results). Skips the year/make/model lookup."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • nhtsa_decode_vin reads unknown 4h ago

    Decode a Vehicle Identification Number to extract make, model, year, body type, engine, safety equipment, and manufacturing details. Pass a single 17-character VIN string, or an array of up to 50 VINs for batch decode. Partial VINs accepted — use * for unknown positions.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "vin"
  ],
  "properties": {
    "vin": {
      "anyOf": [
        {
          "type": "string",
          "description": "A single VIN string (up to 17 characters, * for unknown positions)"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "An array of up to 50 VINs for batch decode"
        }
      ],
      "description": "A single 17-character VIN (e.g., \"1HGCM82633A004352\") or an array of up to 50 VINs for batch decode. Partial VINs accepted — use * for unknown positions."
    },
    "modelYear": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Model year, a whole number. Helps resolve ambiguity for pre-1980 or partial VINs."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • nhtsa_get_vehicle_safety reads unknown 4h ago

    Get a comprehensive safety profile for a vehicle. Combines NCAP crash test ratings, recalls, and complaint summary into a single response. Use as the default when asked about vehicle safety, reliability, or purchase decisions.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "make",
    "model",
    "modelYear"
  ],
  "properties": {
    "make": {
      "type": "string",
      "description": "Vehicle manufacturer (e.g., \"Toyota\", \"Ford\"). Case-insensitive."
    },
    "model": {
      "type": "string",
      "description": "Vehicle model (e.g., \"Camry\", \"F-150\"). Case-insensitive."
    },
    "modelYear": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Model year, a whole number (e.g., 2020)."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • nhtsa_lookup_vehicles reads unknown 4h ago

    Look up valid makes, models, and vehicle types in NHTSA's database. Use to resolve ambiguous vehicle names, find correct make/model spelling, or discover what models a manufacturer produces.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "operation"
  ],
  "properties": {
    "make": {
      "type": "string",
      "description": "Make name (required for \"models\" and \"vehicle_types\"). Partial match supported."
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max results in the returned slice. Defaults to 100; max 200."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Pagination offset into the full result list. Defaults to 0."
    },
    "modelYear": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Filter models to a specific year, a whole number. Only for \"models\" operation."
    },
    "operation": {
      "enum": [
        "makes",
        "models",
        "vehicle_types",
        "manufacturer"
      ],
      "type": "string",
      "description": "\"makes\" (all NHTSA makes), \"models\" (models for a make), \"vehicle_types\" (types for a make), \"manufacturer\" (manufacturer details)."
    },
    "manufacturer": {
      "type": "string",
      "description": "Manufacturer name or ID (for \"manufacturer\" operation). Partial match supported."
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • nhtsa_search_recalls reads unknown 12h ago

    Search recall campaigns by vehicle or campaign number. Use for specific recall lookups, recall history for a vehicle, or looking up a known campaign number.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "make": {
      "type": "string",
      "description": "Vehicle manufacturer. Required with model and modelYear when not using campaignNumber."
    },
    "model": {
      "type": "string",
      "description": "Vehicle model. Required with make and modelYear."
    },
    "dateRange": {
      "type": "object",
      "properties": {
        "after": {
          "type": "string",
          "description": "Only recalls received after this date (ISO 8601, e.g., \"2025-01-01\")."
        },
        "before": {
          "type": "string",
          "description": "Only recalls received before this date (ISO 8601, e.g., \"2026-01-01\")."
        }
      },
      "description": "Filter recalls by received date. Applied locally since the API lacks native date filtering."
    },
    "modelYear": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Model year, a whole number. Required with make and model."
    },
    "campaignNumber": {
      "type": "string",
      "description": "NHTSA campaign number (e.g., \"20V682000\"). When provided, returns the campaign detail plus every vehicle it covers. Mutually exclusive with make/model/modelYear."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 276f606b0b584eca.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/276f606b0b584eca/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/276f606b0b584eca/badge.svg)](https://brick.blue/agent/276f606b0b584eca?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on caseyjhand.com 109 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

101 more sit on this domain. All of them.