The Machine Record MCP

An official MCP server providing read-only access to The Machine Record's public register of incidents involving commercial physical robots, including robotaxis and delivery bots. It allows agents to search cases, retrieve case details with timelines and sources, list companies, view register totals, and query NHTSA Standing General Order crash files without requiring an API key.

Visit The Machine Record

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by The Machine Record

MCP endpoint (Streamable HTTP)

https://themachinerecord.com/api/mcp

Vendor documentation

What you can do with it

Search for specific robot incident cases
Retrieve detailed case timelines and sources
Query NHTSA Standing General Order crash data
List companies and view their profiles

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.themachinerecord/register@1.0.0 Source repository Project website

Maintenance checked: Nov 1, 2026, 8:45 AM UTC

Protocol and capabilities

Server: the-machine-record 1.0.0
MCP protocol: 2025-06-18
Tools: 6 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

The Machine Record is a public register of verified incidents involving commercial robots and autonomous vehicles, each followed from the first report to any investigation, recall, fine, lawsuit or settlement. Use search_cases and get_case for the register, search_nhtsa_sgo for the raw NHTSA crash filings. Cite cases by their permanent URL. Case metadata is CC BY 4.0; the register counts reported incidents, never rates.

Tools

6 advertised

search_cases — Search the register

Advertised by the server during the last successful anonymous check.

Search verified incidents involving commercial robots and autonomous vehicles (robotaxis, delivery robots, humanoids, industrial arms, surgical and consumer robots). Every case has at least two independent sources 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.

search_cases input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "year": {
      "type": "string",
      "pattern": "^\\d{4}$",
      "description": "Year of the incident"
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Rows to return, default 25"
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "description": "Free text matched against title, summary, location, company and robot model"
    },
    "stage": {
      "enum": [
        "report",
        "follow_up",
        "investigation",
        "regulator",
        "recall",
        "fine",
        "lawsuit",
        "settlement",
        "criminal_charge"
      ],
      "type": "string",
      "description": "How far the case has gone after the first report"
    },
    "company": {
      "type": "string",
      "maxLength": 80,
      "description": "Company slug (e.g. waymo) or part of its name"
    },
    "category": {
      "enum": [
        "autonomous_vehicle",
        "delivery",
        "humanoid",
        "robot_arm",
        "industrial",
        "warehouse_amr",
        "surgical",
        "consumer",
        "service",
        "agricultural",
        "other"
      ],
      "type": "string",
      "description": "Kind of machine"
    },
    "severity": {
      "enum": [
        "none",
        "property_damage",
        "minor_injury",
        "serious_injury",
        "fatality"
      ],
      "type": "string",
      "description": "Worst outcome recorded for the case"
    }
  }
}

get_case — Get one case

Advertised by the server during the last successful anonymous check.

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.

get_case input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 200,
      "description": "Case reference like TMR-0123, a slug, or the case URL"
    }
  }
}

list_companies — Companies in the register

Advertised by the server during the last successful anonymous check.

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.

list_companies input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

get_company — Company profile

Advertised by the server during the last successful anonymous check.

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

get_company input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 80,
      "description": "Company slug, e.g. waymo, cruise, starship-technologies"
    }
  }
}

register_totals — Register totals

Advertised by the server during the last successful anonymous check.

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.

register_totals input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

search_nhtsa_sgo — Search NHTSA SGO crash reports

Advertised by the server during the last successful anonymous check.

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.

search_nhtsa_sgo input schema

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 120,
      "description": "Text in narrative, city, report ID, make or model"
    },
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1
    },
    "year": {
      "type": "string",
      "pattern": "^\\d{4}$"
    },
    "crash": {
      "type": "string",
      "maxLength": 60,
      "description": "What the vehicle crashed with, e.g. Passenger Car, Pedestrian, Cyclist"
    },
    "grain": {
      "enum": [
        "report",
        "incident"
      ],
      "type": "string",
      "description": "Default report"
    },
    "state": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2,
      "description": "US state code"
    },
    "entity": {
      "type": "string",
      "maxLength": 120,
      "description": "Reporting entity exactly as filed, e.g. Waymo LLC, Tesla, Zoox"
    },
    "program": {
      "enum": [
        "ADS",
        "ADAS"
      ],
      "type": "string",
      "description": "ADS = driverless, ADAS = Level 2 driver assistance"
    },
    "severity": {
      "type": "string",
      "maxLength": 60,
      "description": "Highest injury severity alleged, e.g. Fatality, Serious, Minor, No Injuries Reported, Unknown"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 1988 ms
95th percentile latency: 1988 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 9:00 AM UTC · probe · passed · 1988 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http the-machine-record-mcp https://themachinerecord.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add the-machine-record-mcp --url https://themachinerecord.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable the-machine-record-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "the-machine-record-mcp": {
      "url": "https://themachinerecord.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "the-machine-record-mcp": {
      "type": "streamableHttp",
      "url": "https://themachinerecord.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start the-machine-record-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "the-machine-record-mcp": {
      "type": "http",
      "url": "https://themachinerecord.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http the-machine-record-mcp https://themachinerecord.com/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "the-machine-record-mcp": {
      "url": "https://themachinerecord.com/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "the-machine-record-mcp": {
      "serverUrl": "https://themachinerecord.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like The Machine Record MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run The Machine Record MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing