What it is

OAuth lets a person grant an agent limited access without sharing a password. With CIMD, an agent’s client ID is a web address that points to a document describing it, so you can see who is asking without a prior registration.

An analogy

A valet key: it opens the car and starts it, but not the glove box or the trunk.

At a glance

Owner
IETF RFCs and the MCP specification
Maturity
Stable The underlying RFCs are stable: protected resource metadata (RFC 9728), authorization server metadata (RFC 8414), dynamic client registration (RFC 7591). MCP’s 2025-11-25 revision made client ID metadata documents (CIMD) the preferred way to identify a client. The 2026-07-28 revision adds issuer checks (RFC 9207).
Where it lives
RFC 9728
Framework domain
Trust: Be trusted
What it serves
  • Let agents act on accounts with consent
  • Limit what an agent can do

Who should care

The roles this standard touches most. See all the roles on the personas page.

  • Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
  • Legal, risk and security. Set the policies: which agents may do what, identity, data, disclosure and liability.

Framework personas →

How to adopt it

  1. 1

    Publish protected resource metadata that points to your sign-in service.

  2. 2

    Accept CIMD clients alongside registered ones.

  3. 3

    Grant narrow scopes, and show people what they approve.

  4. 4

    Log every action an agent takes on an account.

The Institute’s view

Adopt

If an agent will ever act on an account, this is the way to do it. The standards are mature. The work is in choosing scopes and making consent clear to people.

Standards change fast. Last reviewed November 2026.

← Back to the Standards Map