@reclaimprotocol/agent 0.1.27 → 0.1.29

package/src/mcp/api/operations.gen.ts

@@ -1,6 +1,6 @@
 // AUTO-GENERATED by packages/app/scripts/mcp-tools-gen.ts
 // from packages/app/openapi.yaml.
-// Run `npm run openapi:typegen --workspace=packages/agent`
+// Run `npm run openapi:gen --workspace=packages/app`
 // to regenerate. Do not edit by hand.
 // @ts-nocheck
 
@@ -204,12 +204,13 @@ export const MCP_TOOLS = {
 						},
 						"status": {
 							"type": "string",
-							"description": "Status of a verification session, derived from its events. New values\nmay be added over time; clients MUST tolerate unknown values in\nresponses.\n\n- `pending`: Created, not yet finished; completable until `expiresAt`.\n\n- `success`: Terminal — `verification_success` recorded.\n\n- `rejected`: Terminal — `verification_rejected` recorded.\n\n- `error`: Terminal — `verification_error` recorded.\n\n- `expired`: `expiresAt` passed before a terminal event; the end-user\n  can no longer complete it.",
+							"description": "Status of a verification session, derived from its events. New values\nmay be added over time; clients MUST tolerate unknown values in\nresponses.\n\n- `pending`: Created, not yet finished; completable until `expiresAt`.\n\n- `success`: Terminal — `verification_success` recorded.\n\n- `rejected`: Terminal — `verification_rejected` recorded.\n\n- `error`: Terminal — `verification_error` recorded.\n\n- `cancelled`: Terminal — `verification_cancelled` recorded.\n\n- `expired`: `expiresAt` passed before a terminal event; the end-user\n  can no longer complete it.",
 							"enum": [
 								"pending",
 								"success",
 								"rejected",
 								"error",
+								"cancelled",
 								"expired"
 							]
 						},
@@ -234,6 +235,115 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
+	"BindVerificationSessionTeeNonce": {
+		description: "Bind a legacy-compatible TEE nonce to a verification session\n\nBinds one immutable legacy TEE nonce context to a pending session. Requires an OrgToken and an EIP-191 signature from the organization's registered verification key. Repeating the exact binding is idempotent; conflicting or terminal sessions return 409.",
+		inputSchema: toZod({
+			"type": "object",
+			"properties": {
+				"params": {
+					"type": "object",
+					"properties": {
+						"sessionId": {
+							"type": "string",
+							"format": "uuid",
+							"description": "Verification session id (UUID v7 when supported). Also echoed in the result payload as `reclaimSessionId`."
+						}
+					},
+					"required": [
+						"sessionId"
+					],
+					"additionalProperties": false
+				},
+				"query": {
+					"type": "object",
+					"properties": {
+
+					}
+				},
+				"body": {
+					"type": "object",
+					"additionalProperties": false,
+					"description": "One immutable legacy TEE context, signed by the organization verification key. The signature is EIP-191 `personal_sign` over `RECLAIM_BUILDER_TEE_BINDING_V1:{organizationId}:{sessionId}:{applicationId}:{timestamp}:{attestationVersion}:{attestationNonce}`.",
+					"required": [
+						"attestationNonce",
+						"attestationNonceData",
+						"signature"
+					],
+					"properties": {
+						"attestationNonce": {
+							"description": "Either the current lowercase 64-hex hash nonce (without `0x`) or the older 65-byte EIP-191 signature nonce (`0x` plus 130 hex characters). Builder preserves either encoding unchanged.",
+							"oneOf": [
+								{
+									"type": "string",
+									"pattern": "^[0-9a-f]{64}$",
+									"minLength": 64,
+									"maxLength": 64
+								},
+								{
+									"type": "string",
+									"pattern": "^0x[0-9a-fA-F]{130}$",
+									"minLength": 132,
+									"maxLength": 132
+								}
+							]
+						},
+						"attestationNonceData": {
+							"type": "object",
+							"additionalProperties": false,
+							"description": "Exact legacy TEE nonce inputs. Builder stores this unchanged in the session context after it verifies the signed binding request.",
+							"required": [
+								"applicationId",
+								"sessionId",
+								"timestamp",
+								"attestationVersion"
+							],
+							"properties": {
+								"applicationId": {
+									"type": "string",
+									"description": "Ethereum application address derived from the organization private key. Its supplied casing is preserved for legacy nonce compatibility.",
+									"pattern": "^0x[0-9a-fA-F]{40}$",
+									"minLength": 42,
+									"maxLength": 42
+								},
+								"sessionId": {
+									"type": "string",
+									"format": "uuid",
+									"description": "Verification session id (UUID v7 when supported). Also echoed in the result payload as `reclaimSessionId`."
+								},
+								"timestamp": {
+									"type": "string",
+									"description": "Decimal Unix timestamp in milliseconds.",
+									"pattern": "^[0-9]{13}$",
+									"minLength": 13,
+									"maxLength": 13
+								},
+								"attestationVersion": {
+									"type": "string",
+									"description": "Legacy SDK TEE attestation protocol version.",
+									"enum": [
+										"v3"
+									]
+								}
+							}
+						},
+						"signature": {
+							"type": "string",
+							"description": "EIP-191 65-byte secp256k1 signature, encoded as 0x-prefixed hex.",
+							"pattern": "^0x[0-9a-fA-F]{130}$",
+							"minLength": 132,
+							"maxLength": 132
+						}
+					}
+				}
+			},
+			"required": [
+				"params",
+				"query",
+				"body"
+			],
+			"additionalProperties": false
+		}),
+	},
 	"CancelPublicListingRequest": {
 		description: "Cancel a pending public listing review request\n\nCancels a pending public listing request by moving the version from `in_review` back to `draft`. Only org members can cancel their own review requests. This allows users to withdraw a request before admin review if they change their mind.",
 		inputSchema: toZod({
@@ -313,26 +423,65 @@ export const MCP_TOOLS = {
 					"properties": {
 						"callbackUrl": {
 							"type": "string",
-							"format": "uri",
+							"pattern": "^https?://",
+							"description": "Callback URL or template. Supported placeholders are `{{sessionId}}` and top-level scalar context keys.",
 							"maxLength": 2000
 						},
 						"events": {
 							"type": "array",
 							"minItems": 1,
-							"maxItems": 12,
+							"maxItems": 50,
 							"items": {
 								"type": "string",
-								"description": "Lifecycle event reported for a verification session. A healthy run\nproceeds through these in order; reading the gaps locates where a\nsession stalled. Session-level terminal events trigger callback\ndelivery; provider-/request-level events are progress pings carrying a\n`provider_id` (and `request_id` for request-level ones) in their event\ndata. New values may be added over time; clients MUST tolerate unknown\nvalues in responses.\n\n- `session_pending`: Session created; awaiting the end-user.\n\n- `verification_client_opened`: The end-user opened the link. Absent ⇒\n  the link was never opened.\n\n- `verification_client_ready`: The client initialized.\n\n- `verification_provider_started`: The client began verifying a provider\n  (`provider_id`/`resolved_version`/`ordinal` in `eventData`). One per\n  provider, in run order, for multi-provider sessions.\n\n- `request_matched`: The target request was captured on the provider\n  site. Absent (after opened) ⇒ the user didn't complete the journey.\n\n- `request_claim_created`: A proof claim was started.\n\n- `request_claim_completed`: A proof claim finished.\n\n- `request_claim_rejected`: A claim was rejected (detail in `eventData`).\n\n- `request_claim_failed`: A claim errored (detail in `eventData`).\n\n- `verification_success`: Terminal — verified. Triggers callback delivery.\n\n- `verification_rejected`: Terminal — rejected (detail in `eventData`).\n\n- `verification_error`: Terminal — errored (detail in `eventData`).\n\n- `session_expired`: `expiresAt` passed before a terminal event.",
+								"description": "Canonical Builder lifecycle event. Names use lower snake case; metadata uses camel case. Provider events include providerId, resolvedVersion, and ordinal. Request events also include requestId. New values are additive, so clients must tolerate unknown response values. For field requirements and funnel semantics, see docs/verification-analytics-events.md.",
 								"enum": [
+									"billing_required",
 									"session_pending",
 									"verification_client_opened",
 									"verification_client_ready",
+									"verification_client_warning",
+									"verification_client_visibility_shown",
+									"verification_client_visibility_hidden",
+									"verification_diagnostics_mode_changed",
+									"verification_cancelled",
+									"consent_viewed",
+									"consent_scrolled",
+									"consent_agreed",
+									"verification_browser_started",
+									"verification_browser_ready",
+									"verification_browser_reconnect_started",
+									"verification_browser_reconnected",
+									"verification_browser_failed",
 									"verification_provider_started",
+									"provider_config",
+									"provider_script_log",
+									"network_request_observed",
+									"verification_page_ready",
+									"verification_request_interceptor_ready",
+									"verification_provider_completed",
+									"auth_required",
+									"auth_submitted",
+									"auth_challenge_remains",
+									"auth_rejected",
+									"auth_submission_failed",
+									"auth_challenge_completed",
+									"auth_gate_not_detected",
+									"authenticated",
+									"user_interaction_started",
+									"user_input_started",
+									"user_interaction_summary",
+									"verification_inactivity_detected",
 									"request_matched",
+									"request_match_failed",
+									"request_claim_parameters_captured",
 									"request_claim_created",
+									"request_claim_retrying",
 									"request_claim_completed",
 									"request_claim_rejected",
 									"request_claim_failed",
+									"verification_proofs_completed",
+									"verification_result_submitting",
+									"verification_result_submission_failed",
 									"verification_success",
 									"verification_rejected",
 									"verification_error",
@@ -393,7 +542,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"CreateOrgCallbackSubscription": {
-		description: "Register a callback subscription on an organization\n\nRegisters a destination for verification results on the organization. Caller must be an active member of the org. The body is just `callbackUrl` and `events`; delivery is scoped to the org and encrypted as a compact JWE to the org's encryption credential when set, else delivered as plaintext.",
+		description: "Register a callback subscription on an organization\n\nRegisters an organization callback subscription. Pass the callback URL and events to deliver. Builder encrypts signed results when the organization enables result encryption.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -427,26 +576,65 @@ export const MCP_TOOLS = {
 					"properties": {
 						"callbackUrl": {
 							"type": "string",
-							"format": "uri",
+							"pattern": "^https?://",
+							"description": "Callback URL or template. Supported placeholders are `{{sessionId}}` and top-level scalar context keys.",
 							"maxLength": 2000
 						},
 						"events": {
 							"type": "array",
 							"minItems": 1,
-							"maxItems": 12,
+							"maxItems": 50,
 							"items": {
 								"type": "string",
-								"description": "Lifecycle event reported for a verification session. A healthy run\nproceeds through these in order; reading the gaps locates where a\nsession stalled. Session-level terminal events trigger callback\ndelivery; provider-/request-level events are progress pings carrying a\n`provider_id` (and `request_id` for request-level ones) in their event\ndata. New values may be added over time; clients MUST tolerate unknown\nvalues in responses.\n\n- `session_pending`: Session created; awaiting the end-user.\n\n- `verification_client_opened`: The end-user opened the link. Absent ⇒\n  the link was never opened.\n\n- `verification_client_ready`: The client initialized.\n\n- `verification_provider_started`: The client began verifying a provider\n  (`provider_id`/`resolved_version`/`ordinal` in `eventData`). One per\n  provider, in run order, for multi-provider sessions.\n\n- `request_matched`: The target request was captured on the provider\n  site. Absent (after opened) ⇒ the user didn't complete the journey.\n\n- `request_claim_created`: A proof claim was started.\n\n- `request_claim_completed`: A proof claim finished.\n\n- `request_claim_rejected`: A claim was rejected (detail in `eventData`).\n\n- `request_claim_failed`: A claim errored (detail in `eventData`).\n\n- `verification_success`: Terminal — verified. Triggers callback delivery.\n\n- `verification_rejected`: Terminal — rejected (detail in `eventData`).\n\n- `verification_error`: Terminal — errored (detail in `eventData`).\n\n- `session_expired`: `expiresAt` passed before a terminal event.",
+								"description": "Canonical Builder lifecycle event. Names use lower snake case; metadata uses camel case. Provider events include providerId, resolvedVersion, and ordinal. Request events also include requestId. New values are additive, so clients must tolerate unknown response values. For field requirements and funnel semantics, see docs/verification-analytics-events.md.",
 								"enum": [
+									"billing_required",
 									"session_pending",
 									"verification_client_opened",
 									"verification_client_ready",
+									"verification_client_warning",
+									"verification_client_visibility_shown",
+									"verification_client_visibility_hidden",
+									"verification_diagnostics_mode_changed",
+									"verification_cancelled",
+									"consent_viewed",
+									"consent_scrolled",
+									"consent_agreed",
+									"verification_browser_started",
+									"verification_browser_ready",
+									"verification_browser_reconnect_started",
+									"verification_browser_reconnected",
+									"verification_browser_failed",
 									"verification_provider_started",
+									"provider_config",
+									"provider_script_log",
+									"network_request_observed",
+									"verification_page_ready",
+									"verification_request_interceptor_ready",
+									"verification_provider_completed",
+									"auth_required",
+									"auth_submitted",
+									"auth_challenge_remains",
+									"auth_rejected",
+									"auth_submission_failed",
+									"auth_challenge_completed",
+									"auth_gate_not_detected",
+									"authenticated",
+									"user_interaction_started",
+									"user_input_started",
+									"user_interaction_summary",
+									"verification_inactivity_detected",
 									"request_matched",
+									"request_match_failed",
+									"request_claim_parameters_captured",
 									"request_claim_created",
+									"request_claim_retrying",
 									"request_claim_completed",
 									"request_claim_rejected",
 									"request_claim_failed",
+									"verification_proofs_completed",
+									"verification_result_submitting",
+									"verification_result_submission_failed",
 									"verification_success",
 									"verification_rejected",
 									"verification_error",
@@ -599,7 +787,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"CreateProviderVersion": {
-		description: "Create a new provider version\n\nCreates a new version of the provider. The starting branch\ndepends on the provider's `visibility` and the caller's role:\n\n- `PRIVATE` provider (any caller): the live channel (no review).\n\n- `PUBLIC` provider, admin caller (Reclaim staff): the live channel\n  (no review).\n\n- `PUBLIC` provider, non-admin caller: `draft` (or `ai` if\n  authored by the AI assistant). Must pass review (see\n  `POST /providers/{id}/versions/{version}/review`) before\n  reaching the live channel.\n",
+		description: "Create a new provider version\n\nCreates a new immutable semantic version of the provider. Provider\nauthoring clients must create another version for every content change;\nthey must not edit a previously created version in place. Use a patch\nbump by default, or use a major/minor bump or exact higher version when\nthe user directs it. The starting branch\ndepends on the provider's `visibility` and the caller's role:\n\n- `PRIVATE` provider (any caller): the live channel (no review).\n\n- `PUBLIC` provider, admin caller (Reclaim staff): the live channel\n  (no review).\n\n- `PUBLIC` provider, non-admin caller: `draft` (or `ai` if\n  authored by the AI assistant). Must pass review (see\n  `POST /providers/{id}/versions/{version}/review`) before\n  reaching the live channel.\n",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -725,6 +913,15 @@ export const MCP_TOOLS = {
 										"description": "Template used to match or capture an outgoing request body. Template can use regex templates as placeholders. For example, to match an outgoing request body that contains a request ID, you can use the following template: `(?<requestId>.*)`.",
 										"maxLength": 100000
 									},
+									"headers": {
+										"type": "object",
+										"additionalProperties": {
+											"type": "string",
+											"maxLength": 16000
+										},
+										"maxProperties": 100,
+										"description": "Static HTTP request headers passed to the attestor. Header values may use the same `{{param}}` and `{{context.key}}` templates as the URL and request body. Cookies captured by the Verification Client are attached separately and don't need to be declared."
+									},
 									"credentials": {
 										"type": "string",
 										"description": "Mirrors the Fetch API `RequestCredentials` value used when issuing the request — controls whether cookies and auth headers are sent.",
@@ -808,7 +1005,7 @@ export const MCP_TOOLS = {
 									},
 									"responseRedactions": {
 										"type": "array",
-										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
+										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — not generally paired 1:1 with `responseMatches`. For legacy proof-hash optional-subset compatibility only, the redaction at the same index is treated as the pair for an optional `ResponseMatch`; this does not pair all redactions with matches. Mirrors attestor-core `responseRedactions`.",
 										"items": {
 											"type": "object",
 											"additionalProperties": false,
@@ -878,6 +1075,15 @@ export const MCP_TOOLS = {
 										"description": "Template used to match or capture an outgoing request body. Template can use regex templates as placeholders. For example, to match an outgoing request body that contains a request ID, you can use the following template: `(?<requestId>.*)`.",
 										"maxLength": 100000
 									},
+									"headers": {
+										"type": "object",
+										"additionalProperties": {
+											"type": "string",
+											"maxLength": 16000
+										},
+										"maxProperties": 100,
+										"description": "Static HTTP request headers passed to the attestor. Values may contain `{{param}}` and `{{context.key}}` templates."
+									},
 									"credentials": {
 										"type": "string",
 										"description": "Mirrors the Fetch API `RequestCredentials` value used when issuing the request — controls whether cookies and auth headers are sent.",
@@ -961,7 +1167,7 @@ export const MCP_TOOLS = {
 									},
 									"responseRedactions": {
 										"type": "array",
-										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
+										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — not generally paired 1:1 with `responseMatches`. For legacy proof-hash optional-subset compatibility only, the redaction at the same index is treated as the pair for an optional `ResponseMatch`; this does not pair all redactions with matches. Mirrors attestor-core `responseRedactions`.",
 										"items": {
 											"type": "object",
 											"additionalProperties": false,
@@ -1125,7 +1331,7 @@ export const MCP_TOOLS = {
 						},
 						"requiredContext": {
 							"type": "object",
-							"description": "Optional JSON Schema describing the `context` a Consumer must supply when creating a verification session for this provider version. Only needed when the recipe expects Consumer-supplied values: those are referenced as `{{context.<key>}}` in recipe requests. Bare `{{parameterName}}` placeholders are provider parameters (extracted / not Consumer-supplied) and need no declaration here. The Builder validates `CreateVerificationSessionRequest.context` against this schema and rejects the request (400) on mismatch. Extra context fields are always allowed regardless of the schema (a root-level `additionalProperties: false` is ignored). Empty/absent accepts any context.",
+							"description": "Optional JSON Schema describing the `context` a Consumer must supply when creating a verification session for this provider version. Only needed when the recipe expects Consumer-supplied values: those are referenced as `{{context.<key>}}` in recipe requests. Bare `{{parameterName}}` placeholders are normally provider parameters extracted from claimant traffic. For old DevTools recipes, Builder-mode Verification Clients seed a missing bare `parameterName` from a same-named scalar session context field when the recipe doesn't use `{{context.parameterName}}`; an explicit parameter always wins. New recipes should use the explicit `{{context.<key>}}` form. Bare parameters need no declaration here. Builder-owned `reclaimSessionId` and `attestationNonce` remain context-only. The Builder validates `CreateVerificationSessionRequest.context` against this schema and rejects the request (400) on mismatch. Extra context fields are always allowed regardless of the schema (a root-level `additionalProperties: false` is ignored). Empty/absent accepts any context.",
 							"additionalProperties": true
 						},
 						"notes": {
@@ -1145,7 +1351,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"CreateVerificationSession": {
-		description: "Create a verification session\n\nCreates a verification session for an end-user to complete.\nAuthenticated by the consumer's `OrgToken`; the session is scoped to\nthe resolved organization. The request carries no callback URLs —\nresults are delivered to the org's pre-registered callback\nsubscriptions.\n\n    curl -X POST $BASE/verifications/sessions \\\n      -H \"Authorization: Bearer $ORG_TOKEN\" \\\n      -H 'Content-Type: application/json' \\\n      -d '{\"providerId\":\"…\",\"context\":{},\n           \"verificationClientUrl\":\"'$BASE'/v/{sessionId}\"}'\n\nFails with `409 Conflict` if the organization has no callback\nsubscription (there would be nowhere to deliver the result).\n",
+		description: "Create a verification session\n\nCreates an end-user verification session. Requires an OrgToken and a callback subscription; pass providers, context, and an optional registered verificationClientUrl. Billing refusal returns 402 or 429 with event billing_required and a terminal sessionId.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -1188,7 +1394,7 @@ export const MCP_TOOLS = {
 									},
 									"version": {
 										"type": "string",
-										"description": "Semver constraint; empty resolves to the latest trunk version.",
+										"description": "Empty selects the latest active trunk version. An exact semantic version pins that version. Any other valid npm semantic-version range selects the highest active matching version.",
 										"maxLength": 64
 									}
 								}
@@ -1197,17 +1403,28 @@ export const MCP_TOOLS = {
 						"context": {
 							"type": "object",
 							"additionalProperties": true,
-							"description": "Consumer context, shared by all providers. Validated against EACH resolved provider version's `requiredContext` JSON Schema (a 400 is returned on mismatch); extra fields are always allowed. Recipe requests reference these values as `{{context.<key>}}`. Echoed back (plus `reclaimSessionId`) in the result."
+							"description": "Consumer context, shared by all providers. Validated against EACH resolved provider version's `requiredContext` JSON Schema (a 400 is returned on mismatch); extra fields are always allowed. Recipe requests reference these values as `{{context.<key>}}`. To support old DevTools recipes, Builder-mode Verification Clients also use a same-named scalar context value to seed a missing bare `{{key}}` when the recipe doesn't use `{{context.key}}`; an explicit parameter takes precedence. Echoed back (plus `reclaimSessionId`) in the result. Builder-owned `reclaimSessionId` and `attestationNonce` remain context-only."
 						},
 						"verificationClientUrl": {
 							"type": "string",
-							"description": "Optional. Must exactly equal the base URL of a registered verification client (see the `verification_clients` registry / `/admin/verification-clients`). Omit to use the default (`builder`) client. The Builder attaches the session id — into a `{sessionId}` placeholder if the registered base has one, otherwise as a `?sessionId=…` query parameter — and returns the ready-to-share result as `verificationUrl`. A URL that is not a registered client's base is rejected with 400.",
+							"description": "Optional. Must exactly equal the base URL of a registered verification client (see the `verification_clients` registry / `/admin/verification-clients`). Omit to use the default (`builder`) client. The Builder resolves and stores the registered client UUID, then returns the ready-to-share `verificationUrl` with the session id and `api=2`. A URL that is not a registered client's base is rejected with 400. Consumers append any client-owned redirect parameters after receiving the URL; Builder does not manage them.",
 							"maxLength": 2000,
 							"pattern": "^https?://"
 						},
+						"themeId": {
+							"type": "string",
+							"format": "uuid"
+						},
+						"preferredLocale": {
+							"type": "string",
+							"description": "Optional locale override for this verification session. It takes precedence over the organization theme's preferred locale.",
+							"minLength": 2,
+							"maxLength": 64,
+							"pattern": "^[A-Za-z]{2,8}(?:[-_][A-Za-z0-9]{1,8})*$"
+						},
 						"preferAiAgent": {
 							"type": "boolean",
-							"description": "Optional. Whether the Verification Client is preferred (allowed) to run this session's providers with an LLM/AI agent instead of the structured recipe. Omit to default per provider from its `verificationType` (`llm` → agent preferred, `structured` → not). The recipe endpoint exposes the effective per-provider value as `preferAiAgent`. A preference, not a hard gate — clients without agent support run the structured recipe regardless."
+							"description": "Legacy-only preference. Builder mode runs the structured recipe and does not enable AI or manual verification. Omit this field for Builder-mode sessions; dual-mode clients may continue to interpret it only on their legacy path."
 						}
 					}
 				}
@@ -1438,57 +1655,6 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
-	"DeleteProviderVersion": {
-		description: "Delete a provider version\n\nSoft-archives a version on the `draft`, `ai`, or `rejected` branch — sets `status` to `ARCHIVED` so history is preserved. `fixed`, trunk (live), and `in_review` versions cannot be archived this way; archive the parent provider instead. Supports optimistic concurrency via `If-Match`.",
-		inputSchema: toZod({
-			"type": "object",
-			"properties": {
-				"params": {
-					"type": "object",
-					"properties": {
-						"providerId": {
-							"type": "string",
-							"format": "uuid"
-						},
-						"version": {
-							"type": "string",
-							"pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+(?:-[a-zA-Z0-9_-]+(?:\\.[0-9]+)?)?$",
-							"maxLength": 32
-						}
-					},
-					"required": [
-						"providerId",
-						"version"
-					],
-					"additionalProperties": false
-				},
-				"query": {
-					"type": "object",
-					"properties": {
-
-					}
-				},
-				"headers": {
-					"type": "object",
-					"properties": {
-						"If-Match": {
-							"type": "string",
-							"maxLength": 128,
-							"description": "Opaque `ETag` from a prior GET on the same resource. When\nsupplied, the server applies optimistic concurrency: the\nmutation fails with `412 Precondition Failed` if the\nresource has been modified since. Omit for last-write-wins.\n"
-						}
-					}
-				},
-				"body": {
-					"type": "object"
-				}
-			},
-			"required": [
-				"params",
-				"query"
-			],
-			"additionalProperties": false
-		}),
-	},
 	"DiscoverDataPoints": {
 		description: "List the verifiable data points on a website\n\nThe data points existing providers can prove on a website — the menu to pick from before `GET /discover/resolve`. Optionally filter by `q`.",
 		inputSchema: toZod({
@@ -1850,8 +2016,81 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
+	"GetVerificationFunnel": {
+		description: "Get the verification funnel\n\nCalculates an organization's lifecycle funnel for sessions created between required createdAfter (inclusive) and createdBefore (exclusive). Use providerIds/providerMatch and mode (SESSION or PROVIDER) to scope counts. Missing optional events can reflect telemetry loss.",
+		inputSchema: toZod({
+			"type": "object",
+			"properties": {
+				"params": {
+					"type": "object",
+					"properties": {
+						"orgId": {
+							"type": "string",
+							"format": "uuid"
+						}
+					},
+					"required": [
+						"orgId"
+					],
+					"additionalProperties": false
+				},
+				"query": {
+					"type": "object",
+					"properties": {
+						"providerIds": {
+							"type": "array",
+							"minItems": 1,
+							"maxItems": 50,
+							"uniqueItems": true,
+							"items": {
+								"type": "string",
+								"format": "uuid"
+							}
+						},
+						"providerMatch": {
+							"type": "string",
+							"enum": [
+								"ANY",
+								"ALL"
+							],
+							"default": "ANY"
+						},
+						"mode": {
+							"type": "string",
+							"enum": [
+								"SESSION",
+								"PROVIDER"
+							],
+							"default": "SESSION"
+						},
+						"createdAfter": {
+							"type": "string",
+							"format": "date-time"
+						},
+						"createdBefore": {
+							"type": "string",
+							"format": "date-time"
+						}
+					},
+					"required": [
+						"createdAfter",
+						"createdBefore"
+					],
+					"additionalProperties": false
+				},
+				"body": {
+					"type": "object"
+				}
+			},
+			"required": [
+				"params",
+				"query"
+			],
+			"additionalProperties": false
+		}),
+	},
 	"GetVerificationSession": {
-		description: "Get a verification session\n\nReturns the session. Authenticated by the consumer's `OrgToken` (or the\nVC service token); the resolved org must match the session's.\n\nReading `status`:\n- `pending` — created, not yet finished; the end-user can still\n  complete it until `expiresAt`.\n- `success` / `rejected` / `error` — terminal outcomes (the matching\n  `verification_*` event was recorded). Only after a terminal status is\n  a result delivered to callbacks.\n- `expired` — `expiresAt` passed before a terminal event. A `pending`\n  session whose `expiresAt` is in the past has effectively expired and\n  flips to `expired` on the next sweep; the end-user can no longer\n  complete it — issue a fresh session/link.\n\n`callbackDeliveryStatus` aggregates the session's callback deliveries\nand is only meaningful once the session is terminal. To investigate a\nstuck or failed session, pair this with `list_verification_events` (the\nper-stage lifecycle log) and `list_verification_deliveries` (callback\nhealth).\n",
+		description: "Get a verification session\n\nGets one verification session. Use it to inspect status, resolved providers, context, Verification Client identity, and expiry. Present the owning organization token or the session's x-reclaim-vc-id.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -1875,6 +2114,15 @@ export const MCP_TOOLS = {
 
 					}
 				},
+				"headers": {
+					"type": "object",
+					"properties": {
+						"x-reclaim-vc-id": {
+							"type": "string",
+							"description": "UUID of the registered Verification Client selected when the session was created. The Builder binds it to the session's immutable verificationClientId. This header identifies the client; it is not a general bearer credential. Client-reported metadata remains untrusted, and Consumers must verify every signed result with verifyResultFull."
+						}
+					}
+				},
 				"body": {
 					"type": "object"
 				}
@@ -1887,7 +2135,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"ImportDevtoolsProvider": {
-		description: "Import a provider from devtools\n\nImport the latest version of a public provider from the legacy devtools\nservice. Use this when moving an existing provider to Builder instead\nof recreating it.\n\nThe import preserves the legacy provider UUID. The server reads the\ncurrent configuration from\n`https://api.reclaimprotocol.org/api/providers/{providerId}` and\ntranslates it to the Builder schema.\n\nIf the provider already exists in the seeded anonymous catalog, the\nimport assigns that record to the target organization and adds the\nimported version idempotently. A provider owned by another Builder\norganization returns `409`.\n",
+		description: "Import a provider from devtools\n\nImports a public legacy provider into Builder by UUID. Requires human BearerAuth and a target orgId; preserves the provider UUID and is idempotent for seeded providers. Returns 409 if another Builder org owns the UUID.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -2153,12 +2401,13 @@ export const MCP_TOOLS = {
 						},
 						"status": {
 							"type": "string",
-							"description": "Status of a verification session, derived from its events. New values\nmay be added over time; clients MUST tolerate unknown values in\nresponses.\n\n- `pending`: Created, not yet finished; completable until `expiresAt`.\n\n- `success`: Terminal — `verification_success` recorded.\n\n- `rejected`: Terminal — `verification_rejected` recorded.\n\n- `error`: Terminal — `verification_error` recorded.\n\n- `expired`: `expiresAt` passed before a terminal event; the end-user\n  can no longer complete it.",
+							"description": "Status of a verification session, derived from its events. New values\nmay be added over time; clients MUST tolerate unknown values in\nresponses.\n\n- `pending`: Created, not yet finished; completable until `expiresAt`.\n\n- `success`: Terminal — `verification_success` recorded.\n\n- `rejected`: Terminal — `verification_rejected` recorded.\n\n- `error`: Terminal — `verification_error` recorded.\n\n- `cancelled`: Terminal — `verification_cancelled` recorded.\n\n- `expired`: `expiresAt` passed before a terminal event; the end-user\n  can no longer complete it.",
 							"enum": [
 								"pending",
 								"success",
 								"rejected",
 								"error",
+								"cancelled",
 								"expired"
 							]
 						},
@@ -2234,7 +2483,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"ListVerificationDeliveries": {
-		description: "Get the callback delivery status for a session\n\nDiagnostic view of the session's callback deliveries: one entry per\n(subscription, terminal event) with its delivery state, attempt\ncount, last error, and whether it was dead-lettered. Lets a consumer\n(or the agent) answer \"did my callback arrive, and if not, why?\"\nwithout org-dashboard access. Only meaningful after the session\nreaches a terminal status (no deliveries exist before then). Auth\nmirrors the events GET: the Verification Client service token, or the\nconsumer's `OrgToken` (the resolved org must match the session).\n\nReading `deliveryStatus` per entry:\n- `delivered` — the callback POST succeeded; nothing to do.\n- `pending` — queued, not yet attempted (or between retries).\n- `attempt_failed` — a delivery attempt failed but retries remain;\n  `lastError` holds the reason and `attempts` the count so far.\n- `failed` — all retries exhausted. When `deadLettered` is also true\n  the delivery sits in the DLQ.\n\nTo recover a failed/dead-lettered delivery: confirm the `callbackUrl`\nis reachable and answers 2xx, then call `retry_verification_callback`\nto re-enqueue it (an org admin can also retry from the Callback DLQ).\n",
+		description: "Get the callback delivery status for a session\n\nLists callback delivery attempts for a session. Requires an OrgToken or the session-bound x-reclaim-vc-id. Use after terminal status to diagnose pending, failed, or dead-lettered callbacks; retry failures with retry_verification_callback.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -2258,6 +2507,15 @@ export const MCP_TOOLS = {
 
 					}
 				},
+				"headers": {
+					"type": "object",
+					"properties": {
+						"x-reclaim-vc-id": {
+							"type": "string",
+							"description": "UUID of the registered Verification Client selected when the session was created. The Builder binds it to the session's immutable verificationClientId. This header identifies the client; it is not a general bearer credential. Client-reported metadata remains untrusted, and Consumers must verify every signed result with verifyResultFull."
+						}
+					}
+				},
 				"body": {
 					"type": "object"
 				}
@@ -2270,7 +2528,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"ListVerificationEvents": {
-		description: "Get the event log for a session\n\nReturns the append-only event log. Readable by the Verification Client\n(`X-VC-Token`) or the session creator (authenticated by the consumer's\n`OrgToken`; the resolved org must match the session).\n\nThis log is the primary tool for diagnosing a stuck or failed session.\nA healthy run proceeds through this lifecycle (in order):\n\n`session_pending` → `verification_client_opened` →\n`verification_client_ready` → `request_matched` →\n`request_claim_created` → `request_claim_completed` → terminal\n(`verification_success` | `verification_rejected` | `verification_error`),\nor `session_expired` if `expiresAt` passes first.\n\nRead the gaps to locate where the flow stalled:\n- no `verification_client_opened` → the end-user never opened the link.\n- opened but no `request_matched` → the user opened the page but didn't\n  complete the login/journey on the provider site, so the target\n  request was never captured.\n- `request_matched` but no terminal event → the proof run is still in\n  progress (or stalled mid-claim).\n\nFailure detail lives in `eventData` on `request_claim_failed`,\n`request_claim_rejected`, `verification_error`, and\n`verification_rejected` — inspect it for the reason. Request-level\nevents also carry a `request_id` in `eventData`. Pair with\n`get_verification_session` (status/expiry) and\n`list_verification_deliveries` (callback health) for the full picture.\n",
+		description: "Get the event log for a session\n\nLists append-only lifecycle events for a session. Requires an OrgToken or the session-bound x-reclaim-vc-id. Use after get_verification_session to find the first missing or failed milestone; inspect eventData for failure details.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -2294,6 +2552,15 @@ export const MCP_TOOLS = {
 
 					}
 				},
+				"headers": {
+					"type": "object",
+					"properties": {
+						"x-reclaim-vc-id": {
+							"type": "string",
+							"description": "UUID of the registered Verification Client selected when the session was created. The Builder binds it to the session's immutable verificationClientId. This header identifies the client; it is not a general bearer credential. Client-reported metadata remains untrusted, and Consumers must verify every signed result with verifyResultFull."
+						}
+					}
+				},
 				"body": {
 					"type": "object"
 				}
@@ -2984,517 +3251,6 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
-	"UpdateProviderVersion": {
-		description: "Update a provider version\n\nMutable only while the version is on the `draft` or `rejected` branch. Versions on `fixed`, `in_review`, or the live channel reject all writes here. Caller must be a member of the provider's owning organization. Supports optimistic concurrency via `If-Match`.",
-		inputSchema: toZod({
-			"type": "object",
-			"properties": {
-				"params": {
-					"type": "object",
-					"properties": {
-						"providerId": {
-							"type": "string",
-							"format": "uuid"
-						},
-						"version": {
-							"type": "string",
-							"pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+(?:-[a-zA-Z0-9_-]+(?:\\.[0-9]+)?)?$",
-							"maxLength": 32
-						}
-					},
-					"required": [
-						"providerId",
-						"version"
-					],
-					"additionalProperties": false
-				},
-				"query": {
-					"type": "object",
-					"properties": {
-
-					}
-				},
-				"headers": {
-					"type": "object",
-					"properties": {
-						"If-Match": {
-							"type": "string",
-							"maxLength": 128,
-							"description": "Opaque `ETag` from a prior GET on the same resource. When\nsupplied, the server applies optimistic concurrency: the\nmutation fails with `412 Precondition Failed` if the\nresource has been modified since. Omit for last-write-wins.\n"
-						}
-					}
-				},
-				"body": {
-					"type": "object",
-					"additionalProperties": false,
-					"description": "Partial update of a provider version. Mutable only while the version is on the `draft` or `rejected` branch; versions on `fixed`, `in_review`, or the live channel reject all writes here. The semver does not change on update — `build_number` increments instead, giving callers a monotonic revision counter without touching the (major, minor, patch) PK. `verificationType` and `prompt` may be updated; omit either to carry the prior build's value forward.",
-					"properties": {
-						"initialUrl": {
-							"type": "string",
-							"format": "uri"
-						},
-						"verificationType": {
-							"type": "string",
-							"description": "How a provider version verifies a claim. `structured` uses the explicit match rules on this version (the `matches` / `allowedJsMatches` and related settings). `llm` defers the verification decision to a language model and requires `prompt` to be set.",
-							"enum": [
-								"llm",
-								"structured"
-							]
-						},
-						"prompt": {
-							"type": "string",
-							"description": "Extraction prompt, used when `verificationType` is `llm`. Gated by the prompt guard before it is stored (docs/prompt-guard.md).",
-							"minLength": 0,
-							"maxLength": 4000
-						},
-						"requests": {
-							"type": "array",
-							"minItems": 0,
-							"items": {
-								"type": "object",
-								"additionalProperties": false,
-								"description": "A matcher for one HTTP request in observed traffic, together with the response constraints that must hold for a Reclaim proof over that request to be valid. Used by interceptors, in-page injections, and LLM agents.",
-								"required": [
-									"url",
-									"method"
-								],
-								"properties": {
-									"url": {
-										"type": "string",
-										"description": "The URL or generic path of the HTTP request."
-									},
-									"method": {
-										"type": "string",
-										"description": "The HTTP method used for the request.",
-										"enum": [
-											"GET",
-											"POST",
-											"PUT",
-											"PATCH",
-											"DELETE"
-										]
-									},
-									"requestBodyTemplate": {
-										"type": "string",
-										"description": "Template used to match or capture an outgoing request body. Template can use regex templates as placeholders. For example, to match an outgoing request body that contains a request ID, you can use the following template: `(?<requestId>.*)`.",
-										"maxLength": 100000
-									},
-									"credentials": {
-										"type": "string",
-										"description": "Mirrors the Fetch API `RequestCredentials` value used when issuing the request — controls whether cookies and auth headers are sent.",
-										"enum": [
-											"omit",
-											"same-origin",
-											"include"
-										]
-									},
-									"writeRedactionMode": {
-										"type": "string",
-										"description": "How the matched portion of the response should be redacted before the transcript is handed to the attestor.\n- `zk`: redact using a zero-knowledge proof over the original\n  bytes.\n\n- `key-update`: redact by performing a TLS key update so the\n  attestor never observes the matched bytes in cleartext.",
-										"enum": [
-											"zk",
-											"key-update"
-										]
-									},
-									"additionalClientOptions": {
-										"type": "object",
-										"additionalProperties": false,
-										"description": "Apply TLS configuration when creating the tunnel to the attestor.",
-										"properties": {
-											"supportedProtocolVersions": {
-												"type": "array",
-												"description": "TLS protocol versions the client is allowed to negotiate.",
-												"minItems": 1,
-												"uniqueItems": true,
-												"items": {
-													"type": "string",
-													"enum": [
-														"TLS1_2",
-														"TLS1_3"
-													]
-												}
-											}
-										}
-									},
-									"responseMatches": {
-										"type": "array",
-										"description": "Conditions the (redacted) response must satisfy for the proof to be valid. Each runs against the union of the portions revealed by `responseRedactions` (or the whole response when there are none). Mirrors attestor-core `responseMatches`.",
-										"minItems": 1,
-										"items": {
-											"type": "object",
-											"additionalProperties": false,
-											"description": "Specifies a rule to match against a string in response to validate proof content.",
-											"required": [
-												"type",
-												"value"
-											],
-											"properties": {
-												"isOptional": {
-													"type": "boolean",
-													"description": "If true, the match condition is optional and won't fail if absent",
-													"default": false
-												},
-												"description": {
-													"type": "string",
-													"description": "The description of the field that is extracted using this match rule",
-													"minLength": 1,
-													"maxLength": 1000
-												},
-												"order": {
-													"type": "integer",
-													"description": "The order in which the field should be displayed to user in UI",
-													"minimum": 0
-												},
-												"type": {
-													"type": "string",
-													"description": "The matching mechanism to use value as against response. Typically regex or simple string containment",
-													"enum": [
-														"regex",
-														"contains"
-													]
-												},
-												"value": {
-													"type": "string",
-													"description": "The pattern or value to look for in the response. When `type` is 'contains', supports template variable declaration using `{{variable}}` syntax. When `type` is 'regex', can be used to extract variables using regex named groups."
-												}
-											}
-										}
-									},
-									"responseRedactions": {
-										"type": "array",
-										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
-										"items": {
-											"type": "object",
-											"additionalProperties": false,
-											"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (that is, \"HTTP/1.1 200 OK\")",
-											"properties": {
-												"xPath": {
-													"type": "string",
-													"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
-												},
-												"jsonPath": {
-													"type": "string",
-													"description": "expect a JSON response, retrieve the item at this path using dot notation, for example 'email.addresses.0'."
-												},
-												"regex": {
-													"type": "string",
-													"description": "select a regex match from the response"
-												},
-												"hash": {
-													"type": "string",
-													"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
-													"enum": [
-														"oprf",
-														"oprf-mpc",
-														"oprf-raw"
-													]
-												}
-											}
-										}
-									}
-								}
-							}
-						},
-						"allowedJsRequests": {
-							"type": "array",
-							"minItems": 0,
-							"items": {
-								"type": "object",
-								"additionalProperties": false,
-								"description": "A template for selecting requests. Same matcher shape as `RequestSelection`, plus template flags (`multiple`/`required`) and optional `templateParams` expansion.",
-								"required": [
-									"url",
-									"method",
-									"multiple",
-									"required"
-								],
-								"properties": {
-									"url": {
-										"type": "string",
-										"description": "The URL or generic path of the HTTP request."
-									},
-									"method": {
-										"type": "string",
-										"description": "The HTTP method used for the request.",
-										"enum": [
-											"GET",
-											"POST",
-											"PUT",
-											"PATCH",
-											"DELETE"
-										]
-									},
-									"requestBodyTemplate": {
-										"type": "string",
-										"description": "Template used to match or capture an outgoing request body. Template can use regex templates as placeholders. For example, to match an outgoing request body that contains a request ID, you can use the following template: `(?<requestId>.*)`.",
-										"maxLength": 100000
-									},
-									"credentials": {
-										"type": "string",
-										"description": "Mirrors the Fetch API `RequestCredentials` value used when issuing the request — controls whether cookies and auth headers are sent.",
-										"enum": [
-											"omit",
-											"same-origin",
-											"include"
-										]
-									},
-									"writeRedactionMode": {
-										"type": "string",
-										"description": "How the matched portion of the response should be redacted before the transcript is handed to the attestor.\n- `zk`: redact using a zero-knowledge proof over the original\n  bytes.\n\n- `key-update`: redact by performing a TLS key update so the\n  attestor never observes the matched bytes in cleartext.",
-										"enum": [
-											"zk",
-											"key-update"
-										]
-									},
-									"additionalClientOptions": {
-										"type": "object",
-										"additionalProperties": false,
-										"description": "Apply TLS configuration when creating the tunnel to the attestor.",
-										"properties": {
-											"supportedProtocolVersions": {
-												"type": "array",
-												"description": "TLS protocol versions the client is allowed to negotiate.",
-												"minItems": 1,
-												"uniqueItems": true,
-												"items": {
-													"type": "string",
-													"enum": [
-														"TLS1_2",
-														"TLS1_3"
-													]
-												}
-											}
-										}
-									},
-									"responseMatches": {
-										"type": "array",
-										"description": "Conditions the (redacted) response must satisfy for the proof to be valid. Each runs against the union of the portions revealed by `responseRedactions` (or the whole response when there are none). Mirrors attestor-core `responseMatches`.",
-										"minItems": 1,
-										"items": {
-											"type": "object",
-											"additionalProperties": false,
-											"description": "Specifies a rule to match against a string in response to validate proof content.",
-											"required": [
-												"type",
-												"value"
-											],
-											"properties": {
-												"isOptional": {
-													"type": "boolean",
-													"description": "If true, the match condition is optional and won't fail if absent",
-													"default": false
-												},
-												"description": {
-													"type": "string",
-													"description": "The description of the field that is extracted using this match rule",
-													"minLength": 1,
-													"maxLength": 1000
-												},
-												"order": {
-													"type": "integer",
-													"description": "The order in which the field should be displayed to user in UI",
-													"minimum": 0
-												},
-												"type": {
-													"type": "string",
-													"description": "The matching mechanism to use value as against response. Typically regex or simple string containment",
-													"enum": [
-														"regex",
-														"contains"
-													]
-												},
-												"value": {
-													"type": "string",
-													"description": "The pattern or value to look for in the response. When `type` is 'contains', supports template variable declaration using `{{variable}}` syntax. When `type` is 'regex', can be used to extract variables using regex named groups."
-												}
-											}
-										}
-									},
-									"responseRedactions": {
-										"type": "array",
-										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
-										"items": {
-											"type": "object",
-											"additionalProperties": false,
-											"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (that is, \"HTTP/1.1 200 OK\")",
-											"properties": {
-												"xPath": {
-													"type": "string",
-													"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
-												},
-												"jsonPath": {
-													"type": "string",
-													"description": "expect a JSON response, retrieve the item at this path using dot notation, for example 'email.addresses.0'."
-												},
-												"regex": {
-													"type": "string",
-													"description": "select a regex match from the response"
-												},
-												"hash": {
-													"type": "string",
-													"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
-													"enum": [
-														"oprf",
-														"oprf-mpc",
-														"oprf-raw"
-													]
-												}
-											}
-										}
-									},
-									"multiple": {
-										"type": "boolean",
-										"description": "If true, the template is allowed for multiple requests. Useful for requests like paginated API calls.",
-										"default": true
-									},
-									"required": {
-										"type": "boolean",
-										"description": "If true, a request is required to match with this template. If not requests matches this template in proof, then validation fails.",
-										"default": true
-									},
-									"templateParams": {
-										"type": "array",
-										"description": "Names of `${param}` placeholders used in this template's `responseMatches` / `responseRedactions`, substituted at verification time from array-valued extracted parameters (each name must resolve to an array of values; all named arrays must have the same length). Absent or empty means the template is used as-is with no expansion.",
-										"maxItems": 50,
-										"items": {
-											"type": "string",
-											"minLength": 1,
-											"maxLength": 100
-										}
-									},
-									"templateParamsMode": {
-										"type": "string",
-										"description": "How array values of `templateParams` expand the template: `separate` (default) emits one expanded request — its own claim — per value; `merge` emits a single request whose `responseMatches`/`responseRedactions` contain all substituted entries, proven by one claim.",
-										"enum": [
-											"separate",
-											"merge"
-										],
-										"default": "separate"
-									}
-								}
-							}
-						},
-						"webSettings": {
-							"type": "object",
-							"additionalProperties": false,
-							"description": "Settings used by the web-based verification client.",
-							"properties": {
-								"geoLocation": {
-									"type": "string",
-									"description": "Geographic location the verification should appear to originate from: a 2-letter ISO country code, or a parameter the attestor resolves at proof time. `{{DYNAMIC_GEO}}` and `{{DYNAMIC_GEO_SECRET}}` are the Verification Client's standard names for the end-user's own country — the `_SECRET` one is delivered as a secret param, so the attestor never learns which country the proof egressed from.",
-									"maxLength": 64,
-									"default": "{{DYNAMIC_GEO}}"
-								},
-								"clientOptions": {
-									"type": "object",
-									"additionalProperties": false,
-									"description": "Options that influence how the web verification client behaves.",
-									"properties": {
-										"portal": {
-											"type": "object",
-											"additionalProperties": false,
-											"description": "Options that influence how the portal verification client behaves.",
-											"properties": {
-												"useProxy": {
-													"type": "boolean",
-													"description": "When true, network traffic from the portal client and attestation is routed through a proxy.",
-													"default": true
-												},
-												"userAgent": {
-													"type": "string",
-													"description": "User-agent string used for platform verification.",
-													"maxLength": 500
-												}
-											}
-										},
-										"inapp": {
-											"type": "object",
-											"additionalProperties": false,
-											"description": "Options that influence how the in-app verification client behaves.",
-											"properties": {
-												"interceptorOptions": {
-													"type": "object",
-													"additionalProperties": false,
-													"required": [
-														"interceptorType"
-													],
-													"properties": {
-														"interceptorType": {
-															"type": "string",
-															"description": "How traffic interception is implemented.",
-															"enum": [
-																"HAWKEYE",
-																"MSWJS",
-																"CDP"
-															]
-														},
-														"isDocumentRequestReplayEnabled": {
-															"type": "boolean",
-															"description": "Whether the main document request is replayed via the attestor",
-															"default": false
-														},
-														"interceptorSettings": {
-															"type": "string",
-															"description": "Free-form configuration passed through to the interceptor implementation selected by `interceptorType`. Keys and value shapes are defined by the chosen interceptor.",
-															"contentMediaType": "application/json"
-														}
-													}
-												},
-												"userAgents": {
-													"type": "object",
-													"additionalProperties": false,
-													"description": "User-agent strings keyed by platform.",
-													"properties": {
-														"android": {
-															"type": "string",
-															"description": "User-agent string used for platform verification.",
-															"maxLength": 500
-														},
-														"ios": {
-															"type": "string",
-															"description": "User-agent string used for platform verification.",
-															"maxLength": 500
-														}
-													}
-												}
-											}
-										},
-										"extension": {
-											"type": "object",
-											"description": "Free-form key-value configuration for the browser-extension verification client. Keys and value shapes are defined by the extension client; values may be any JSON. Absent by default.",
-											"maxProperties": 100,
-											"additionalProperties": true
-										}
-									}
-								},
-								"jsUserScripts": {
-									"type": "string",
-									"description": "JavaScript snippets injected into the page which runs before every page load. `window.Reclaim.` APIs are available to these scripts to request actions to the client like claim creation.",
-									"maxLength": 1000000
-								}
-							}
-						},
-						"requiredContext": {
-							"type": "object",
-							"description": "Optional JSON Schema describing the `context` a Consumer must supply when creating a verification session for this provider version. Only needed when the recipe expects Consumer-supplied values: those are referenced as `{{context.<key>}}` in recipe requests. Bare `{{parameterName}}` placeholders are provider parameters (extracted / not Consumer-supplied) and need no declaration here. The Builder validates `CreateVerificationSessionRequest.context` against this schema and rejects the request (400) on mismatch. Extra context fields are always allowed regardless of the schema (a root-level `additionalProperties: false` is ignored). Empty/absent accepts any context.",
-							"additionalProperties": true
-						},
-						"notes": {
-							"type": "string",
-							"description": "Free-form change note recorded on `updateMetadata`.",
-							"maxLength": 10000
-						}
-					}
-				}
-			},
-			"required": [
-				"params",
-				"query",
-				"body"
-			],
-			"additionalProperties": false
-		}),
-	},
 }
 
 export type McpToolName = keyof typeof MCP_TOOLS