Anthropic published the Model Hardware Standard on 27 August, a device-description format that lets AI agents drive microscopes, liquid handlers, plate readers and robot arms. The company describes it as "a shared specification for AI agents to safely operate physical devices," opened "to a first group of scientific research labs and advanced manufacturers." The claimed effect is cutting instrument integration from "weeks, if not months" to "hours or minutes."

What the partners reported

At the University of Washington, a PhD student connected six instruments in under a week. Carnegie Mellon reported serial dilution runs roughly three times faster, with integration taking about eight hours against several weeks for a typical vendor setup. HHMI Janelia, where the project originated, unified seven separate vendor programs behind one interface. QuEra Computing automated laser recovery at 99.3% success across 700 trials, cutting recovery from five to ten minutes down to seconds. Genentech automated a BCA protein assay across a liquid handler, robotic arm and plate reader.

It is deliberately not a Claude product

MHS is model-agnostic. Anthropic states it works with "any device that has a programmable interface" over standard protocols including MCP, CLI and plain APIs — and that it functions with no language model in the loop at all. Named partners include AWS, Automata, Danaher, Doosan Robotics, MBF Bioscience, QIAGEN, Tecan, Universal Robots, Hugging Face and Raspberry Pi. Anthropic also concedes Claude "struggles with physical, chemical, and biological constraints," needing guidance on matters as basic as bubble formation in liquid handling.

What the common framing gets wrong

The word doing the damage is "standard." This is a research preview handed to a named cohort, with a waitlist. Anthropic says it "plans to open source it in the future" — future tense, with no date, no licence and no public specification repository. Coverage calling MHS released, open or available is describing something that does not exist yet. The MCP comparison is Anthropic's own analogy, not a status: MCP shipped as a public spec with an SDK on day one, while MHS shipped as an access list. And "Anthropic enters robotics" overreads it — MHS is a description-and-safety-envelope file format in which a vendor declares permitted speeds and angles. It is not a control model and not an embodied model.

The regulatory wrinkle almost nobody carried

EU Machinery Regulation 2023/1230 applies from 20 January 2027. An MHS file that performs a safety function may need formal conformity assessment rather than self-declaration — which would turn what looks like a configuration file into a regulated safety component inside seventeen months.