The Provely MCP server has 4 tools. This page lists each tool and each argument from the tool definitions of the server.

Which tools does the server have?

Tool	Title	What it does
`provely_begin`	Begin a Provely operation	Open a Provely operation before you do a side-effecting action. Returns the operation id and the correlation and idempotency metadata to use in the action. A successful tool call is not proof of completion. Only a verdict from Provely is. PENDING is a normal answer: the action is not done yet.
`provely_verify`	Verify a Provely operation	Submit the action result, when you have not yet, and ask the Provely runtime to verify the operation against its completion contract. Returns the verdict: VERIFIED, PENDING, CONTRADICTED, FAILED, or UNVERIFIABLE. Report it exactly. A successful tool call is not proof of completion. Only a verdict from Provely is. PENDING is a normal answer: the action is not done yet.
`provely_status`	Read the status of a Provely operation	Read the state and the last verdict of a Provely operation. Use it to resume an operation from any session by id. A successful tool call is not proof of completion. Only a verdict from Provely is. PENDING is a normal answer: the action is not done yet.
`provely_receipt`	Fetch the receipt of a Provely operation	Fetch the signed evidence receipt of a Provely operation. A receipt exists only after a verdict. Validate it offline with the trusted key map of the SDK or the CLI. A successful tool call is not proof of completion. Only a verdict from Provely is. PENDING is a normal answer: the action is not done yet.

Which arguments does `provely_begin` take?

Argument	Type	Required	What it holds
`contract_id`	`string`	yes	The contract identity. Example: stripe.refund.succeeded.
`contract_version`	`string`	yes	The contract version. The control plane needs it. Example: 1.4.2.
`input`	`map`	no	The caller input of the contract as a JSON object.
`intent`	`string`	no	The intent statement. What the user asked for.
`confirmation_id`	`string`	no	The confirmation that a person gave for this contract. A contract that an intent compilation wrote runs only after a person confirms it. Send the identity that the confirmation answered. The server reads the record and refuses an identity that it does not hold. A contract that a person wrote by hand needs no confirmation.
`provider_api_version`	`string`	no	The provider API version in effect for the action.
`project`	`string`	no	The project name. Optional.
`idempotency_key`	`string`	no	A key that makes a retry of begin safe.

Which arguments does `provely_verify` take?

Argument	Type	Required	What it holds
`operation_id`	`string`	yes	The operation id from begin.
`action_result`	`map`	no	Send it once, on the first verify call, when you did not submit it before.
`action_result.status`	`acknowledged \| error \| unknown`	yes	acknowledged: the provider replied. error: it replied with an error. unknown: no reply.
`action_result.evidence_level`	`E0 \| E1`	no	E0 is a bare agent claim. E1 is a relayed provider response. The default follows result.
`action_result.result`	`value`	no	The provider response body as you received it.
`action_result.error`	`map`	no	-
`action_result.error.code`	`string`	no	-
`action_result.error.message`	`string`	no	-
`action_result.transport`	`map`	no	-
`action_result.transport.protocol`	`string`	no	-
`action_result.transport.status_code`	`integer`	no	-
`action_result.transport.request_id`	`string`	no	-
`action_result.idempotency_key`	`string`	no	-
`action_result.provider_api_version`	`string`	no	-
`action_result.started_at`	`string`	no	-
`action_result.completed_at`	`string`	no	-

Which arguments does `provely_status` take?

Argument	Type	Required	What it holds
`operation_id`	`string`	yes	The operation id from begin.

Which arguments does `provely_receipt` take?

Argument	Type	Required	What it holds
`operation_id`	`string`	yes	The operation id from begin.

How do I register the server?

A local server over stdio: provely mcp

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

The hosted server

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

Where this page comes from

A generator writes this page from the files below. A test fails when the page differs from them.

File	Commit	Committed
`packages/mcp`	`f5f2e1bf`	2026-10-17

Which tools does the server have?

Which arguments does provely_begin take?

Which arguments does provely_verify take?

Which arguments does provely_status take?

Which arguments does provely_receipt take?

How do I register the server?

Which arguments does `provely_begin` take?

Which arguments does `provely_verify` take?

Which arguments does `provely_status` take?

Which arguments does `provely_receipt` take?