Skip to main content
Glama

Server Details

Verified robot and AV incidents, first report to court outcome, plus the NHTSA SGO crash file

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct entity or dataset: single case, single company, company list, global totals, verified case search, and raw NHTSA filing search. The only potential confusion is between search_cases and search_nhtsa_sgo, but the descriptions explicitly separate verified incidents from operator self-filings, which resolves it.

Naming Consistency4/5

Five of six tools follow a clean verb_noun pattern (get_case, get_company, list_companies, search_cases, search_nhtsa_sgo) with correct singular/plural handling. register_totals breaks the pattern slightly by reading as a noun compound rather than verb_noun, but it is still readable and unambiguous.

Tool Count5/5

Six tools is well-scoped for a read-only research database: a search, two entity lookups, a company listing, and two aggregate/report views. Nothing feels redundant or missing at the count level.

Completeness4/5

Core workflows are covered: find cases, drill into a case, drill into a company, browse companies, and get totals plus a parallel NHTSA dataset. Minor gaps exist, such as no direct way to query or filter by source tier, incident category, or date range across cases, but agents can work around these via search and get_case.

Available Tools

6 tools
get_caseGet one caseAInspect

Full record of one case by its reference (TMR-0123) or URL slug: summary, machine, dated timeline of what each source established, the sources with their tier and archive copy, and any linked NHTSA Standing General Order report.

Inputs: id (required).

get_companyCompany profileBInspect

One company's cases with harm and escalation counts, breakdown by incident type, and the category average for comparison.

Inputs: slug (required).

list_companiesCompanies in the registerAInspect

Every company with at least one published case: number of cases, how many went beyond the first report, and the share. Not a safety ranking: the register counts reported incidents, not incidents per machine.

Inputs: no named parameters.

register_totalsRegister totalsAInspect

Headline numbers: cases, cases that reached a regulator, recall or court, archived sources, companies, earliest year, last update, cases by country, and totals of the NHTSA Standing General Order file.

Inputs: no named parameters.

search_casesSearch the registerAInspect

Search verified incidents involving commercial robots and autonomous vehicles (robotaxis, delivery robots, humanoids, industrial arms, surgical and consumer robots). Each case is traced to its sources (press cases are checked against independent domains at publication) and is followed from first report to investigation, recall, fine, lawsuit or settlement. Returns case summaries with permanent URLs; use get_case for the timeline and sources.

Inputs: year, limit, query, stage, +3 more.

search_nhtsa_sgoSearch NHTSA SGO crash reportsAInspect

Crash reports filed under NHTSA's Standing General Order 2021-01 by automated driving system (ADS) and Level 2 driver assistance operators, 2021 to today, one row per report at its latest version, or one row per incident when grain is 'incident' (filings by several entities about one crash collapsed at the highest severity). Rows are the operators' own filings, not verified cases, and a filing does not establish fault.

Inputs: q, page, year, crash, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources