The gap MCP leaves open
MCP authorization answers whether a client may call a server. OAuth binds the token to the endpoint and can carry the user and organization identity. It does not record what the person allowed the agent to do, at which merchant, for how much, or for how long. Attesso adds the missing layer:- a bounded mandate the person approves with a passkey;
- a deterministic decision for every proposed action;
- one execution of one allowed authorization;
- a signed record a third party verifies without trusting Attesso.
The MCP Test Drive
The test drive is one complete loop, not a mock:- The agent asks for one bounded test payment.
- The person approves the exact terms with a passkey in the browser.
- The agent reads the state, authorizes the action, commits once, and fetches the receipt.
- The receipt is verified against the published keys.
request_id and the exact
error. We will reproduce it and tell you whether the failure is in the client,
the endpoint, or the action.
Connect
- Add
https://mcp-test.attesso.com/mcpto an MCP client that supports remote HTTP and OAuth 2.1. - Let the client discover
https://mcp-test.attesso.com/.well-known/oauth-protected-resource/mcpand open the Clerk sign-in. The requested scopes areprofile,email, anduser:org:read. - Complete the sign-in with the Attesso account that should own the test request.
- Ask the agent to call
request_spendwith a stablerequest_id, an amount in minor units, a currency, and an optional merchant and purpose. - Open the returned
approval_urland approve the exact terms with a passkey. - Call
approval_statusuntil the mandate isACTIVE, thenauthorize_action. Proceed only whencan_executeis exactlytrue. - Call
commit_actiononce with the executor reference, then callget_receiptand verify the envelope.
Tools
The public surface is five intent tools. They map one-to-one to the lifecycle; a use case changes the approved terms, not the tool list.
The test limit is 100000 minor units per request. An execution window is between
60 and 3600 seconds and defaults to 900.
Example request
request_spend returns a mandate and an approval URL. It does not approve the
request.
Example decision
can_execute: true. A DENY is final for that proposed action;
do not rewrite it into a new request under the same authority.
Failure semantics
PENDING_APPROVALis not permission. Never execute on it.can_execute: falseis a refusal. Read the reason; do not retry the same action under the same authorization.get_receiptreturnsRECEIPT_NOT_READYuntil the mandate has been committed.- A single-use mandate is consumed by the first commit. A second commit is rejected.
- Reusing a
request_idwith different terms returnsIDEMPOTENCY_CONFLICT. - A tenant with too many open mandates returns
OPEN_MANDATE_LIMIT. - Approval is always the subject’s hosted passkey ceremony. There is no approve tool and no API-key approval path.
Receipt verification
get_receipt returns a compact JWS in the attesso.evidence.v1 format. Verify
ES256 over the exact ASCII bytes of protected.payload with the key whose kid
appears in protected. The public keys are at:
Use cases
The test server demonstrates the payment action. The same shape carries the actions an agent actually takes:- Invoice payments: exact payee, amount to the cent, currency, and reference.
- Travel: route, dates, cabin, property, and amount bounds.
- Procurement: one purchase order inside a vendor, amount, and date window.
- AI and compute spend: a recurring budget with a per-period cap.
commit_action.
Test-only boundaries
- The server holds the commitment opening for this test path only. A live integration keeps the opening with its own client.
- The endpoint makes no payment and authorizes no live money.
- The test endpoint is not a production authority.
- The endpoint claims no MCP conformance. It is a test surface for the authorization and evidence loop.

