MCP server: begin, verify, status, receipt

The MCP server exposes four tools: begin, verify, status, and receipt. Hosted mode serves streamable HTTP with a bearer token. Local mode runs provely mcp over stdio. No tool takes an API key.

Tool	Input	Output
`begin`	`contract`, `input`	operation id, idempotency key, correlation keys
`verify`	`operation_id`	verdict, reason, evidence levels used
`status`	`operation_id`	operation state, last verdict
`receipt`	`operation_id`	the signed receipt document

Every tool description carries the core rule: a successful tool call is not proof of completion. The server reads the bearer token inside each tool handler and never returns a credential.

How do I register the server?

.mcp.json for a local stdio server

{
  "mcpServers": {
    "provely": {
      "command": "provely",
      "args": ["mcp"]
    }
  }
}

The hosted server

{
  "mcpServers": {
    "provely": {
      "type": "http",
      "url": "https://api.provely.sh/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

How does an agent drive the four tools?

Use the MCP tools from an agent

Call begin.Pass the contract id and the input. Keep the operation id and the idempotency key.
Do the action.Use the idempotency key in the provider request.
Call verify.Pass the operation id. Read the verdict.
Report the verdict as returned.On PENDING, give the operation id and call status later. On VERIFIED, call receipt.

Which agents support MCP today?

Claude Code, Cursor, Codex, the OpenAI Agents SDK, and LangGraph state MCP support in their profiles. OpenClaw, pi, and Grok are marked verify at implementation. Read the agent pages.