Model Context Protocol (MCP)
An open protocol for connecting AI systems to external data sources and tools through a client–server interface. A host application runs clients; each client connects to a server that exposes a declared set of resources, tools and prompts.
Why it matters for autonomous finance
MCP is the first widely adopted place where an agent's reach is declared rather than assumed. A server exposes an explicit tool surface, which means the question 'what is this agent permitted to touch' has a machine-readable answer for the first time. For governance purposes that server manifest is an authority grant, and it should be treated as a controlled document — versioned, reviewed, and diffed on change.
What it does not cover
MCP describes capability, not permission. It says what an agent can reach; it does not say what it may commit, under whose authority, or up to what limit. Reading a tool manifest as an authorization boundary is the most likely governance mistake of the next two years — the protocol was never designed to carry that weight.
Says nothing about oversight intervals, drift, or accountability. Every entry in this register carries this section. A standard read past its scope is worse than no standard, because it produces confidence without coverage.
Read it
Other standards in the register
Source and provenance
- Issuing body
- Anthropic; open specification
- Canonical source
- https://modelcontextprotocol.io/
- Version
- Not recorded
- Last verified
- Not recorded
- Content held
- This corpus holds no copy of the source's text; the record is a citation, and no content digest can be given.
- Third-party material
- The framework, its text, identifiers and version belong to its issuing body (Anthropic; open specification). This corpus cites it, reproduces none of its text, and grants no rights in it.
- This corpus's work
- The summary, why-it-matters, caveat, gap statement and MARQUE mapping on this page are this corpus's own editorial work, under the terms at https://qistrust.com/license/.
No dated claim about this source is recorded in the verification register; its locator and description were not re-verified against the source for this record. The same record, field for field, is in api/provenance.json (qis-provenance-1) and in this page's structured data.