The Model Hardware Standard on 27 August 2026 is a research preview, then open source
The Model Hardware Standard is Anthropic's research preview from 27 August 2026 for AI agents that operate physical devices. It is invite-only; the named successor is an open-source standard after partner safety work. MCP is one of three access paths, not a rival product. Pexon sizes GPU and residency first and does not treat MHS as something you can buy.
Deadline
What the 27 August 2026 note actually changes
| What changes | From | What replaces it |
|---|---|---|
| Who can speak to lab and factory devices | Weeks or months of bespoke drivers per instrument | An MHS driver with read/write primitives, claimed in hours or minutes |
| How an agent reaches that driver | No common interface across vendors | MCP, a command line, or code files — three mechanisms, not one product |
| What you can buy today | Nothing. There is no SKU | An invite-only research preview; Anthropic names open source as the successor after partner safety work |
Every cell is from Anthropic's 27 August 2026 announcement. No general-availability date is published.
Anthropic opened a preview, not a catalogue item
On 27 August 2026 Anthropic published a research preview of the Model Hardware Standard: a shared specification for AI agents to operate physical devices, starting with scientific labs and advanced manufacturers. The note names microscopes, liquid handlers and robotic arms. Development began with HHMI Janelia. Typical integration, Anthropic writes, takes weeks if not months; MHS is claimed to cut that to hours or minutes for any device with a programmable interface.
The same page is explicit about what this is not. Access is an application to a preview. The driver is model-agnostic. Any agent harness can reach it through standard protocols such as the Model Context Protocol, and Anthropic lists three control paths together: MCP, the CLI, and code files. The named successor is not a paid SKU. It is making the standard open source after they have built safety evaluations with partners.
Before you apply
What to do with the preview if you run an EU estate
- Inventory programmable interfaces, not brand names. MHS only attaches to a device that already has a programmable interface. If the instrument is a GUI with no API, the CMU write-up on the same page had to drive the screen. That is a different project from a driver.
- Decide where the driver's logs live. The announcement does not specify residency for the natural-language tags, the reference file, or the telemetry the agent reads back. That gap is yours to fill before an agent writes a set-temperature command in a regulated lab.
- Budget GPU for the agent loop, not only the instrument. The University of Washington note on the same page says long monitoring windows have compute costs that must be weighed against researcher time. Size that separately from the liquid handler.
Must be true before the preview is useful to you
- Invite You can apply. Anthropic has not said the preview is open to every manufacturer.
- Safety file Someone will write the natural-language tags and the enforced safety limits. That is an operations job, not a download.
- Successor You can live with invite-only until open source ships. There is no published day for that ship.
Trade-off
If you have no programmable instruments this quarter, or you need a generally available hardware standard on a procurement calendar, doing nothing is the right answer. The 27 August 2026 note is a preview for a first group of labs and manufacturers, not a replacement for the stack you already run.
Date and successor are both taken from Anthropic's 27 August 2026 announcement, read 14 September 2026: research preview now; open source after partner safety evaluations. No other date is used.
Size the box before you talk to the preview
- AI server sizing — the money page for owned inference hardware in the same cluster
- GPU inference sizing — how many cards before an agent loop runs overnight
- Private AI hub — open-weight models on hardware you control
Questions after the 27 August 2026 note
What is the Model Hardware Standard?
It is a shared driver spec for agents that operate physical devices. Anthropic opened a research preview on 27 August 2026 with labs and manufacturers. It is not a product SKU and not generally available.
How is MHS different from MCP?
MCP is one of three ways an agent reaches MHS, next to a CLI and code files. MHS is the hardware driver and safety-limit file; MCP is a protocol the harness already speaks. They stack, they do not replace each other.
When does MHS become open source?
Anthropic has not published a calendar day. The 27 August 2026 note says they are running the preview with partners to build safety evaluations ahead of making the standard open source. Until that ship date exists, treat open source as the named successor, not a schedule.
What does an MHS setup cost?
Anthropic does not list a licence price. Partner notes on the same page give integration time (hours versus weeks) and warn that long agent loops have compute cost. A Pexon two-week blueprint is €4,900 net if you need GPU and residency sized before you apply to the preview.
When should we ignore MHS for now?
If you have no programmable instruments, or you need a generally available standard this quarter, skip it. The preview is invite-only. Doing nothing is correct until you have a device list and a residency rule for the telemetry the driver will emit.
Next step
Size the hardware before you apply for the preview
Two weeks, €4,900 net: GPU count, residency of the logs the driver will emit, and whether MHS is even the right interface for the instruments you already own. The note is yours to keep.