Every lab we have ever worked near keeps the same drawer of vendor software. Seven programs, seven serial protocols, nothing that talks to anything else. Anthropic opened a research preview of the Model Hardware Standard on 27 August 2026, and MHS is the swing at making that drawer go away: one driver format per device, exposing read and write plus network discovery, so an agent can find a microscope or a liquid handler and drive it. Two things the headlines got wrong. It is not a rival to MCP. It sits underneath, and MCP is one of three ways to reach it. And you cannot have it yet. No spec, no repo, no reference driver. There is an application form.
The short answer
Anthropic wants one driver format for microscopes and robot arms, with safety limits living in the driver instead of a prompt. The idea is good and the partner numbers are striking. You still cannot build against it, because nothing has been published.
What MHS actually standardises
A driver. That is the whole trick, and it is smaller than the announcement makes it sound.
Today a robotic arm speaks whatever its manufacturer decided in 2014, a microscope ships a Windows program with a scripting tab, and gluing them into one experiment means somebody writes serial glue for a fortnight. MHS says: give each device a driver that exposes the same tiny surface. Read, as in get temperature. Write, as in set temperature. Plus discovery, so devices and agents can find each other across a network in a standard format.
Then the interesting bit. The driver carries natural-language tags, which compile into a reference file the agent reads before it touches anything. That file says what the device can measure, what is adjustable, and where the safety limits are. Physical facts too, like how much a given arm weighs.
Which means the guardrail is in the driver, not the system prompt. Honestly, that is the design decision I would defend if I only got to keep one. Prompt-level safety is per-agent and evaporates the moment somebody swaps harnesses. A limit compiled into the driver applies to every caller, including the one you did not anticipate.
The MCP comparison is doing damage
Plenty of write-ups framed this as Anthropic doing for hardware what it did for software. Fair enough as a slogan. It is wrong as architecture.
MCP is a protocol between an agent and a tool server. MHS is a device driver contract underneath that. Anthropic’s own text names three ways to orchestrate a device: MCP, a command line, and code files. If you already run an MCP server or two, MHS does not replace them. It gives them something consistent to sit on top of, roughly the way WebMCP gave ChatGPT’s Site tools a defined surface inside a browser instead of a pile of button-guessing.
So the honest one-liner is duller than the headline. MHS standardises the boring layer nobody wants to own.
The numbers, and who counted them
QuEra Computing gives the loudest one. A laser relock routine on its neutral-atom hardware, previously handled by a bespoke script that worked 58 percent of the time and burned 150 seconds an attempt, hit a 99.3 percent success rate across 700 trials under MHS, recovering in under six seconds for easy disturbances and 10 to 14 seconds for hard ones.
Carnegie Mellon reports going from raw equipment to a finished dose-response protocol in eight hours, against the several weeks a vendor integration usually eats, and running the experiments about three times faster. A University of Washington group connected six instruments in under a week. Janelia collapsed a microscopy workflow from seven separate vendor programs into one dashboard click.
Every one of those came from a preview partner, and none of them ship a methodology. I would not put any of it in a business case yet.
The number I trust most is the failure. At Genentech, Claude tuned an automated protein assay to roughly 140 microlitres a second for water and 10 for a protein solution, then bubbles formed and it could not tell a physical problem from a software bug. Anthropic says this out loud: Claude learns the physical world through text and images, so its spatial reasoning has limits that still need expert oversight. Good. A standard that pretends otherwise would be worse than no standard.
What you can do with this today
Nothing, and I want to be blunt about it because the coverage was not.
There is no specification document. No reference driver, no repository, no schema for the reference file. modelhardwarestandard.com is a landing page with an application form for organisations in science, robotics and manufacturing. Anthropic says it will open source the standard once preview partners have helped build safety evaluations, and it has published no date for that.
If you run anything with a programmable control surface, the vendor list is the signal to watch. Universal Robots and Doosan on arms, QIAGEN and Tecan on lab kit, AWS on the agent side, and Raspberry Pi sitting there for whoever wants to prototype a driver on a 60 dollar board once the spec exists. A standard nobody implements is a blog post. That list is the closest thing to evidence that this one might not be.
We will pick it up again when there is a file to read. Until then it is a good idea with a waiting list.
Sources
The announcement and the partner results are from Anthropic’s Previewing the Model Hardware Standard post of 27 August 2026, plus the application page at modelhardwarestandard.com. Independent coverage and the driver-level detail were cross-checked against The Decoder and MarkTechPost. For the protocol layer above it, see our notes on the MCP roadmap after the 2026-07-28 spec.
Frequently asked questions
What is the Model Hardware Standard?
MHS is a shared specification, previewed by Anthropic on 27 August 2026, for letting AI agents discover and operate physical equipment. Each device gets an MHS driver that translates between the operating system and the hardware using a small primitive set: read (get temperature), write (set temperature) and discovery across a network. The driver also carries natural-language tags that compile into a reference file describing what a device measures, what can be adjusted, and which safety limits get enforced.
Does MHS replace the Model Context Protocol?
No, and this is the part most coverage flattened. Anthropic lists three ways to drive an MHS device: MCP, a command line, and code files. MCP is one route into the layer, not the layer itself. MHS is also described as model agnostic, so any agent harness can reach it through standard protocols. Think of MHS as the driver and MCP as one of the doors, rather than as MCP version two for robots.
Can I download the spec or a driver today?
Not as of 31 August 2026. There is no published specification, no reference implementation and no repository. modelhardwarestandard.com is an application form for a gated research preview, open to organisations in science, robotics and manufacturing. Anthropic says it intends to open source the standard after building safety evaluations with preview partners, but it has attached no date to that.
Who is already building on it?
Anthropic names research partners including Genentech, QuEra Computing, Carnegie Mellon, HHMI Janelia Research Campus, Tetsuwan Scientific and two University of Washington labs. On the vendor side it lists Amazon Web Services with Strands Robots, Automata, Danaher, Doosan Robotics, MBF Bioscience, QIAGEN, Tecan, Universal Robots, Hugging Face and Raspberry Pi. The Raspberry Pi entry is the one worth watching if you want to prototype cheaply once the spec lands.
How good are the performance numbers Anthropic published?
They are partner-reported, with no methodology paper behind them. QuEra says a laser relock task went from a bespoke script succeeding 58 percent of the time at 150 seconds per attempt to a 99.3 percent success rate over 700 trials. Carnegie Mellon reports eight hours of driver work against several weeks for a vendor setup. Treat those as vendor case studies until somebody outside the preview reproduces them.
