Is the Olyport Nhtsa MCP server down?

mcp-registry/com.olyport/nhtsa · v1.26.0

healthy
Last checked 2026-10-26 20:37 UTC · handshake 22ms

As of 2026-10-26 20:37 UTC, the Olyport Nhtsa MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
100%
checks observed
4,892
outages (90d)
1
tools
6

Vehicle safety recalls, complaints, and crash data from NHTSA

Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/nhtsa/mcp

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 6 tool(s); ~1,187 tokens of tool definitions.
Scores higher than 11% of 15,760 MCP servers Glimind has audited.
Its tool list costs an agent ~1,187 tokens per session — lighter than 70% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (2)

14 parameter(s) across 6 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: complaint_trends_by_component, decode_vin, get_complaints, get_crash_statistics, get_recalls and 1 more

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: complaint_trends_by_component, decode_vin, get_complaints, get_crash_statistics, get_recalls and 1 more

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.olyport%2Fnhtsa/fixes

get_complaints 1 change 
{
  "name": "get_complaints",
  "description": "Get consumer complaints about vehicles filed with NHTSA.\n\n    Search for safety complaints by make, model, and/or year. Returns\n    complaint descriptions, components involved, and crash/injury data.\n    At least one filter (make, model, or year) should be provided.\n\n    Args:\n        make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford').\n        model: Vehicle model name (e.g. 'Camry', 'F-150').\n        year: Model year (e.g. 2023).\n        limit: Maximum number of complaints to return (defau",
  "inputSchema": {
    "type": "object",
    "title": "get_complaintsArguments",
    "properties": {
      "make": {
        "type": "string",
        "title": "Make",
        "default": null
      },
      "year": {
        "type": "integer",
        "title": "Year",
        "default": null
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 25
      },
      "model": {
        "type": "string",
        "title": "Model",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_crash_statistics 1 change 
{
  "name": "get_crash_statistics",
  "description": "Get fatal crash statistics from the NHTSA Fatality Analysis Reporting System (FARS).\n\n    Returns fatal motor vehicle crash data for a state, including total\n    fatalities, fatalities by person type (drivers, passengers, pedestrians),\n    and alcohol-involved crashes.\n\n    Args:\n        state: Two-digit state FIPS code (e.g. '06' for California, '48' for Texas)\n            or two-letter state abbreviation (e.g. 'CA', 'TX').\n        year: Year for statistics (e.g. 2022). Defaults to the most rec",
  "inputSchema": {
    "type": "object",
    "title": "get_crash_statisticsArguments",
    "required": [
      "state"
    ],
    "properties": {
      "year": {
        "type": "integer",
        "title": "Year",
        "default": null
      },
      "state": {
        "type": "string",
        "title": "State"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_recalls 1 change 
{
  "name": "get_recalls",
  "description": "Get vehicle safety recalls from NHTSA.\n\n    Search for recalls by make, model, and/or year. Returns recall campaigns\n    including the defect description, remedy, and affected vehicles.\n    At least one filter (make, model, or year) should be provided.\n\n    Args:\n        make: Vehicle manufacturer name (e.g. 'Toyota', 'Ford', 'Honda').\n        model: Vehicle model name (e.g. 'Camry', 'F-150', 'Civic').\n        year: Model year (e.g. 2023).\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_recallsArguments",
    "properties": {
      "make": {
        "type": "string",
        "title": "Make",
        "default": null
      },
      "year": {
        "type": "integer",
        "title": "Year",
        "default": null
      },
      "model": {
        "type": "string",
        "title": "Model",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.olyport/nhtsa"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.olyport/nhtsa"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fnhtsa.svg)](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fnhtsa?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fnhtsa?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fnhtsa.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fnhtsa.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fnhtsa?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:060efff376fe9757…, first seen 2026-10-17, included at leaf 14086 of 75,347. Version history · verify what your client received.

Tools (6)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Olyport Nhtsa MCP server down right now?

As of 2026-10-26 20:37 UTC, the Olyport Nhtsa MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 9 minutes.

How many tools does Olyport Nhtsa MCP server provide?

Olyport Nhtsa MCP server advertises 6 tools, including complaint_trends_by_component, decode_vin, get_complaints, get_crash_statistics, get_recalls.

How do I install Olyport Nhtsa MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/nhtsa/mcp

Is the Olyport Nhtsa MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Olyport Nhtsa MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve