FREE CORE MACHINE AUTHORITY
Authority for machines that act.
MCPaios governs authority as the operational implementation of the MCP2 Machine Authority & Evidence Profile. It separates what a machine can technically reach from what it is authorized to do—and produces the evidence needed to prove the difference later.
Core MCPaios access is free. External infrastructure and other products may have their own costs.
THE OPERATING QUESTION
Does this machine possess valid, bounded, unrevoked authority to perform this exact action against this exact target now?
And can that decision later be proven?
SYSTEM INDEX
One authority system. Distinct technical layers.
Explore the protocol, operating plane, trust boundaries, and proof model as separate parts of one governed execution path.
What Is MCPaios
The operational implementation of MCP2: human decisions, machine identities, grants, fences, receipts, revocation, and reconstruction.
How Machine Authority Works
The eight-stage path from machine proposal through human decision, local execution, evidence, reconstruction, and revocation.
MCP2 Protocol
The protocol that determines whether a machine possesses valid authority for an exact action, target, purpose, and moment.
Use Cases
Authority boundaries for agents, automated workflows, infrastructure operations, regulated systems, and developer platforms.
Evidence & Reconstruction
Portable reconstruction evidence and a preserved historical production proof.
Security & Trust
Fail-closed enforcement, local credential custody, least-privilege roles, current trust, and precise nonclaims.
AUTHORITY IS NOT CAPABILITY
A credential may make execution possible. It does not make execution authorized.
MCPaios keeps the execution credential at the target boundary and evaluates authority independently. A machine proposal cannot ratify itself. A stale grant cannot become current by being replayed. A receipt cannot be substituted for the decision it was meant to record.
Examine the trust boundaries →REQUEST → RECORD
A complete machine-authority lifecycle.
Machine proposal, human decision, bounded grant, fence verification, local execution, receipt, reconstruction, and revocation each perform a separate job. No stage silently authorizes the next.
HISTORICAL PROOF · SEPTEMBER 3, 2026
ALLOW before local execution. DENY after human revocation.
A preserved September 3 production proof exercised machine proposal, human ratification, exact grant issuance, receipted ALLOW, local completion, reconstruction, revocation, later GRANT_NOT_ACTIVE DENY, and retirement of the temporary service credentials.
BUILT FOR CONSEQUENTIAL SYSTEMS
For machines that can do more than generate text.
Organizations deploying agents, workflow operators, infrastructure teams, regulated systems, and developers can add a provable authority decision without surrendering their target runtime.
OPEN PROTOCOL · OPERATIONAL PRODUCT
MCP2 defines machine authority. MCPaios puts it to work.
MCP2 — Machine Authority & Evidence Profile defines how bounded, current, revocable machine authority is evaluated and reconstructed. It is not “MCP version 2,” and it does not replace the Model Context Protocol.
MCPaios supplies the human and machine operating surfaces around that protocol: proposals, identities, ratification, grants, execution fences, receipts, revocation, reports, and reconstruction.
Read the protocol overview →HUMAN AUTHORITY PLANE
Operate machine authority from one controlled record.
Review what machines request, see what they hold, revoke what must stop, and reconstruct what happened.