The Machine Record
REMOTE · THEMACHINERECORD.COM
Verified robot and AV incidents, first report to court outcome, plus the NHTSA SGO crash file
Available components
Last scanned (42 minutes ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://themachinerecord.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=themachinerecord.com | CN=YR1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 6598258316c2e0fa9d7c315e99f6efd0169 |
| SANs: themachinerecord.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of themachinerecord.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| themachinerecord.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://themachinerecord.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://themachinerecord.com/api/mcp | HTTPS enforced | 308 | https://themachinerecord.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_case Get one case ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Case reference like TMR-0123, a slug, or the case URL |
No output schema declared.
No examples provided.
get_company Company profile ~51
One company's cases with harm and escalation counts, breakdown by incident type, and the category average for comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Company slug, e.g. waymo, cruise, starship-technologies |
No output schema declared.
No examples provided.
list_companies Companies in the register ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_totals Register totals ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_cases Search the register ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
search_nhtsa_sgo Search NHTSA SGO crash reports ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
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.
remote · themachinerecord.com
claude mcp add --transport http com-themachinerecord-register 'https://themachinerecord.com/api/mcp'
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.