# The Machine Record (remote · themachinerecord.com)

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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `themachinerecord.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-themachinerecord-register/api-mcp.md), [page](https://verifymcp.io/servers/com-themachinerecord-register/api-mcp)

## Channel facts

- Endpoint: `https://themachinerecord.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 760 tokens (~126/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the The Machine Record MCP server?

The Machine Record is a hosted endpoint at https://themachinerecord.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-themachinerecord-register 'https://themachinerecord.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-themachinerecord-register": {
      "url": "https://themachinerecord.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-themachinerecord-register": {
      "type": "http",
      "url": "https://themachinerecord.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-themachinerecord-register]
url = "https://themachinerecord.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-themachinerecord-register": {
      "type": "remote",
      "url": "https://themachinerecord.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-themachinerecord-register --url 'https://themachinerecord.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-themachinerecord-register:
    url: "https://themachinerecord.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-themachinerecord-register": {
      "Transport": "http",
      "Url": "https://themachinerecord.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-themachinerecord-register -t streamable-http -u 'https://themachinerecord.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-themachinerecord-register": {
      "type": "http",
      "url": "https://themachinerecord.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 65)

First indexed and scored.

## MCP tools (6)

### `search_cases` (~183 tokens)

Search the register

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.

Input parameters:

- `category` (string): Kind of machine
- `company` (string): Company slug (e.g. waymo) or part of its name
- `limit` (integer): Rows to return, default 25
- `query` (string): Free text matched against title, summary, location, company and robot model
- `severity` (string): Worst outcome recorded for the case
- `stage` (string): How far the case has gone after the first report
- `year` (string): Year of the incident

### `get_case` (~82 tokens)

Get one case

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.

Input parameters:

- `id` (string, required): Case reference like TMR-0123, a slug, or the case URL

### `list_companies` (~50 tokens)

Companies in the register

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.

### `get_company` (~51 tokens)

Company profile

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

Input parameters:

- `slug` (string, required): Company slug, e.g. waymo, cruise, starship-technologies

### `register_totals` (~52 tokens)

Register totals

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.

### `search_nhtsa_sgo` (~253 tokens)

Search NHTSA SGO crash reports

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.

Input parameters:

- `crash` (string): What the vehicle crashed with, e.g. Passenger Car, Pedestrian, Cyclist
- `entity` (string): Reporting entity exactly as filed, e.g. Waymo LLC, Tesla, Zoox
- `grain` (string): Default report
- `page` (integer)
- `program` (string): ADS = driverless, ADAS = Level 2 driver assistance
- `q` (string): Text in narrative, city, report ID, make or model
- `severity` (string): Highest injury severity alleged, e.g. Fatality, Serious, Minor, No Injuries Reported, Unknown
- `state` (string): US state code
- `year` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-themachinerecord-register/api-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 66
- 2026-10-27: 66
- 2026-10-26: 65

## Common questions

### What is the The Machine Record MCP server?

The Machine Record is an MCP server listed in the public MCP registry as com.themachinerecord/register. Verified robot and AV incidents, first report to court outcome, plus the NHTSA SGO crash file. This page covers its hosted endpoint (https://themachinerecord.com/api/mcp).

### Is the The Machine Record MCP server safe to use?

The Machine Record scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the The Machine Record MCP server expose?

The Machine Record exposes 6 tools: search_cases, get_case, list_companies, get_company, register_totals, search_nhtsa_sgo. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.

### Does the The Machine Record MCP server require authentication?

No. We connected to The Machine Record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The Machine Record MCP server still maintained?

The Machine Record is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://themachinerecord.com/api/mcp
- Repository: https://github.com/vzolot/tmr-pipeline
- Website: https://themachinerecord.com/data
- Changelog RSS feed: https://verifymcp.io/servers/com-themachinerecord-register/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-themachinerecord-register/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-themachinerecord-register/api-mcp