Skip to content
MCPaiosMachine Authority
Explore
MCPaios/What Is MCPaios

PRODUCT DEFINITION

The operational implementation of MCP2.

MCPaios is the operational implementation of the MCP2 Machine Authority & Evidence Profile. It gives humans a control plane, gives machines constrained identities, and places a receipted authority fence in front of protected execution.

MCPAIOS / FREE CORE / AUTHORITY-PLANE

FREE CORE ACCESS

No MCPaios subscription or usage fee for core authority.

Use the core authority system without an MCPaios paywall. External infrastructure, hosting, provider services, integrations, and other MAXAIOS products may have separate costs. Free access does not change source licensing. PayMAXAIOS is not required for ordinary MCPaios use; paid actions have a separate financial decision.

THE PROBLEM

Machines often possess capability without a provable authority decision.

An agent may hold an API token. A workflow may know a production endpoint. An automation may have the technical ability to alter infrastructure, move data, or trigger an external system. None of those facts proves that the machine is authorized for this exact action, against this exact target, for this purpose, at this moment.

MCPaios makes that missing authority explicit. It records the machine proposal, requires an authenticated human decision, issues only the bounded grant that was ratified, verifies current state at the target boundary, and records what followed.

The result is not a reusable permission popup. It is a current authority record that can be revoked, inspected, and reconstructed.

CAPABILITYcan performAUTHORITYmay perform now

OPERATING SURFACES

Every surface has one authority job.

Identity, decision, execution, and evidence remain distinct so that no convenient interface quietly expands machine power.

01

Human authority plane

Authenticated people review exact proposals, ratify or deny them, and retain the power to revoke authority.

02

Machine identity plane

Separate operator, fence, and auditor identities prevent one credential from becoming universal machine power.

03

Authority ledger

Grants bind actor, action, target, purpose, policy, time, and ratification into a current authority record.

04

Execution boundary

The target-side fence evaluates current state immediately before any protected side effect.

05

Evidence plane

Decision receipts, completion evidence, revocation events, and reconstruction remain linked without rewriting history.

WHO IT IS FOR

Systems where machine actions have consequences.

Organizations deploying agents

Put a governed authority decision between autonomous requests and consequential systems.

Automated workflow operators

Replace standing credentials and implied permission with exact, time-bounded grants.

Infrastructure teams

Keep production credentials at the target while an independent fence evaluates authority.

Regulated systems

Preserve the human decision, machine scope, execution result, and later authority changes.

Developers

Integrate proposal, verification, receipt, and reconstruction contracts without adopting a hosted execution runtime.

Examine the use cases →

PUBLIC / PRIVATE BOUNDARY

The website informs. The login opens the product.

The public pages explain MCP2, MCPaios, integration, evidence, and security without requiring an account. The Control Plane exposes decisions, grants, people, machine identities, evidence, reconstruction, reports, integration, and revocation only to authenticated members.

Open the authenticated Control Plane →
PUBLICProtocol and product information
PROTECTEDMachine-authority operations
TARGETLocal credentials and execution

CLEAR NONCLAIMS

What MCPaios is not.

Not MCP v2. MCP2 is the Machine Authority & Evidence Profile, not a new version of MCP.

Does not replace MCP. Connection and authority are separate problems.

Does not centrally execute customer actions. Protected targets execute locally after ALLOW.

Credentials do not equal authority. Technical possession cannot authorize itself.

OPERATE THE BOUNDARY

Understand the system publicly. Operate it privately.

The Control Plane remains the authenticated working area for human decisions, machine identities, grants, receipts, revocation, and reconstruction.

Open the Control Plane