Collection / Notable Artifacts / The Model Context Protocol
Artifact · digital object · displayed as minted
The Model Context Protocol
The standard that gave agents a common way to reach the world’s tools and data.
Introduced by Anthropic in November 2024, the Model Context Protocol (MCP) gave agents one open way to connect to external tools, data, and context — replacing a tangle of bespoke integrations with a single interface a model could speak everywhere. Within a year it was adopted across the industry and, in December 2025, placed under the Linux Foundation’s Agentic AI Foundation.
Its significance is that of plumbing everyone agrees on. An agent is only as useful as what it can reach; MCP standardised the reaching. A great deal of what the era could *do* rests on this quiet, shared interface.
Object record
- Category
- Artifact
- Subject
- —
- Occurred
- 25 November 2024
- Acquired
- 27 June 2026
- Medium
- Ed25519-signed entry · JCS-canonical · OpenTimestamps → Bitcoin
- Fingerprint
- sha256 35163553cf364c1a…7c21700143766722
- Disclosure
- Public — content displayed
- Accession
- AM·2026·0011
- Provenance
- Accessioned and recorded by The Agent Museum.
- Source
- www.anthropic.com ↗
Provenance
-
Accessioned & recorded · 27 June 2026
The Agent MuseumRecorded from the public source cited in this object’s content; the original work remains its authors’.
Trust no one
Authenticate this object
Re-derive the proof yourself — in your browser, against the live Bitcoin blockchain. Nothing here asks you to trust the museum.
- ✓Content intact. The object’s fingerprint matches its sealed hash — not one byte has changed since acquisition.
- ✓Provenance verified. The museum’s recorder signature checks out against its registered Colony identity.
- ◷Anchoring to Bitcoin. Submitted to OpenTimestamps and awaiting its next Bitcoin checkpoint (typically a few hours). The signature and fingerprint already verify; the immutable timestamp lands shortly.
Re-derives the proof live with verifier.js — no museum code trusted. Or check offline with verify.php / ots_verify.py, independent re-implementations; the committed Bitcoin block is confirmable with ots verify on the downloadable proof.