@reclaimprotocol/agent 0.1.31 → 0.1.33

package/skill/SKILL.builder.md

@@ -367,7 +367,10 @@ developer it's awaiting admin review.
 context params — for example, `context: { "username": "…" }` in
 `create_verification_session`. Quote the `requiredContext` from the created
 version verbatim — a session missing those fields gets a 400, and verification
-matches the supplied values exactly.
+matches the supplied values exactly. Then ask once how they want to use it —
+try it now here, integrate it into an existing backend or frontend, or create a
+new app — unless they already said (see "Using a provider" in the server
+instructions).
 
 **6. If the response includes `_notes` for an attached browser, follow them for
 an optional authenticated-state retest.** Only when its profile is still signed
@@ -391,9 +394,18 @@ use, run the same flow the Discover UI does:
 3. `discover_resolve({ domain, dataPoints })` → the smallest provider set
    (`providers`, greedy combine), the `requiredContext` inputs to collect, and
    any `uncovered` points (author those with the flow above, then re-resolve).
-4. `create_verification_session({ providers: [{ providerId }, …], context,
+4. Resolved providers are published and usable as-is: don't capture, replay,
+   or prove them unless the developer asks you to check or test one. Ask once
+   whether they just want to try them or want them in an app — just try it
+   now, integrate into an existing backend or frontend (this directory or
+   another path), or create a new app — unless they already said.
+5. Just try it (no app, callback, or client package) →
+   `create_verification_session({ providers: [{ providerId }, …], context,
    verificationClientUrl })` with EVERY resolved provider id and the collected
-   context.
+   context, give them `verificationUrl`, poll `get_verification_session` until
+   it is terminal, and report the outcome with `get_verification_result`
+   (builder-mode instructions cover the org key and temporary callback).
+   Integrate or new app → topic `integration`.
 
 `merge.mergeable` only signals the set *could* collapse into one provider — you
 still pass them all; the Builder runs them in one session.

package/skill/SKILL.old.md

@@ -318,8 +318,10 @@ applies them.
   would fetch. Reads the public production SDK backend directly, no auth.
 
 There's no create-then-version step and no org / public-review workflow here.
-When done, tell the developer the version is live and that they can integrate
-using the `providerId`.
+When done, tell the developer the version is live, then ask once how they want
+to use it — try it now, integrate it into an existing backend or frontend, or
+create a new app — unless they already said (see "Using a provider" in the
+server instructions).
 
 **If the response includes `_notes` for an attached browser, follow them for an
 optional authenticated-state retest.** Only when its profile is still signed in,

package/skill/builder-mode.md

@@ -6,12 +6,55 @@ authoring tools.
 
 ## Claimant-facing Builder sessions
 
-This integration is separate from provider authoring. When asked to set up an
-app, read `how_it_works({ topic: "integration" })`, then configure the
-organization with generated tools (`list_orgs`, `create_org`,
-`create_org_callback_subscription`, and owner-only `issue_org_token`) and edit
-the app's frontend and backend with the coding agent's file tools. The guide
-covers the `@reclaimprotocol/client` workflow, exact `api=2` boundary, result
+This integration is separate from provider authoring.
+
+**Using a provider.** A provider found with `providers`, `discover_resolve`, or
+another lookup is published and usable as-is. Don't capture, `replay_request`,
+or `run_proof` against it unless the developer asks you to check or test it.
+Before using a provider, found or just created, ask once whether they just want
+to try it or want it in an app (skip this if they already said):
+
+> Want to (1) just try it right now, (2) integrate it into an existing backend
+> or frontend (this directory or another path), or (3) create a new app for it?
+
+- **Just try it:** no app or client package, but the same production API the
+  app will use. You need an org API key (`rorg_…`): reuse one the developer
+  already has, else `issue_org_token` (owner only; the key is shown once).
+  Session creation returns 409 while the org has no callback subscription, and
+  the result is only stored for subscriptions to the event the session ends
+  with. If the org has none, register a temporary one for all five ending
+  events with `create_org_callback_subscription` (for example, a tunnel to a
+  local listener that saves the body it receives). Then call
+  `create_verification_session` with `orgToken`, give the developer
+  `verificationUrl` to open, poll `get_verification_session` (with `orgToken`)
+  until it is terminal, and report the outcome: from the body your listener
+  received, or with `get_verification_result` (with `orgToken`), which only
+  works until the callback is delivered. Delete the temporary subscription with
+  `delete_org_callback_subscription` only after that: deleting it also deletes
+  its stored results.
+- **Integrate, or new app:** follow the setup below in the path they named.
+
+**Org API key vs. sign-in.** Management tools (`list_orgs`,
+`create_org_callback_subscription`, `issue_org_token`, …) use the developer's
+sign-in. Session tools (`create_verification_session`,
+`get_verification_session`, `list_verification_events`,
+`list_verification_deliveries`, `retry_verification_callback`) are the
+production API a backend calls, so they take the org key as `orgToken`
+(defaulting to this server's `RECLAIM_ORG_SECRET`). Never print the key back to
+the developer.
+
+**Prefer the HTTP API over `@reclaimprotocol/client`** for every option:
+create sessions with `POST /verifications/sessions`, open `verificationUrl`,
+poll `GET /verifications/sessions/{sessionId}`, and take the result on the
+callback. Use the client package only when the developer asks for it — the one
+exception is `results.receive`, to verify the result on your callback.
+
+When integrating into an app, read `how_it_works({ topic: "integration" })`,
+then configure the organization with generated tools (`list_orgs`,
+`create_org`, `create_org_callback_subscription`, and owner-only
+`issue_org_token`) and edit the app's frontend and backend with the coding
+agent's file tools. The guide
+covers the HTTP session workflow, exact `api=2` boundary, result
 verification, request-proof contract, and optional TEE binding. A URL without
 `api=2` stays on its existing legacy path.
 
@@ -21,15 +64,15 @@ else:
 
 > This project uses `@reclaimprotocol/js-sdk`. Keep it (I switch this MCP
 > server to legacy devtools mode), or migrate to the Builder integration
-> (`@reclaimprotocol/client`)?
+> (Builder HTTP API)?
 
 - **Keep js-sdk:** call `set_devtools_mode({ mode: "old" })`, then tell them to
   restart or reconnect the MCP server; the switch applies on the next start. An
   explicit `USE_OLD_DEVTOOLS` env var overrides it. After the restart, read
   `get_js_sdk_integration_guide`.
 - **Migrate:** stay in Builder mode. Follow `how_it_works({ topic:
-  "integration" })` to replace `@reclaimprotocol/js-sdk` with
-  `@reclaimprotocol/client` and update the app's code.
+  "integration" })` to replace `@reclaimprotocol/js-sdk` with the Builder
+  HTTP session flow and update the app's code.
 
 **A `provider` is a recipe for extracting a data point from a site. A
 `verification` is an end-user session that proves a data point using one. Never

package/skill/old-mode.md

@@ -55,6 +55,18 @@ existing provider instead; you can only version a provider you own. For a
 multi-request provider pass `providers: [draftA, draftB, …]` so each becomes a
 parallel `requestData` entry on the one version.
 
+**Using a provider.** A provider found with `get_me_providers` or
+`get_provider_info` is published and usable as-is. Don't capture,
+`replay_request`, or `run_proof` against it unless the developer asks you to
+check or test it. Before using a provider, found or just created, ask once how
+they want to use it (skip this if they already said):
+
+> Want to (1) try it right now here, (2) integrate it into an existing backend
+> or frontend (this directory or another path), or (3) create a new app for it?
+
+Try it now → `scaffold_reclaim_demo_server` with its `providerId`. Integrate,
+or new app → `get_js_sdk_integration_guide`, then work in the path they named.
+
 **Two independent auth systems — don't confuse them.** `reclaim_authenticate`
 authorizes everything in this mode; its Firebase token is short-lived (~1h), so
 an auth error on publish or `get_me_providers` means re-run it.

package/skill/verification-client-integration.md

@@ -9,7 +9,7 @@ configure Builder resources; the coding agent's file tools edit the app.
 
 If the app depends on `@reclaimprotocol/js-sdk`, ask the developer first:
 keep it (call `set_devtools_mode({ mode: "old" })` and have them restart the MCP
-server), or migrate to `@reclaimprotocol/client` with the steps below. When
+server), or migrate to the Builder session flow below. When
 migrating, remove `@reclaimprotocol/js-sdk` and replace its
 `ReclaimProofRequest` and `verifyProof` calls with the session flow below.
 
@@ -21,19 +21,24 @@ migrating, remove `@reclaimprotocol/js-sdk` and replace its
    error, cancellation, and expiry events. If the app needs encrypted results,
    register its public key with `set_org_keypair`; retain the private key only
    in the backend.
-3. An organization owner can call `issue_org_token`. Its `orgSecret` is shown
-   once. Put it in the app backend's secret configuration as
-   `RECLAIM_ORG_SECRET`; keep it out of frontend bundles, logs, source control,
-   and the final response. Reuse an already configured secret when available;
-   issue a new token when setup needs one.
-4. Install `@reclaimprotocol/client` in the backend. Use
-   `ReclaimVerification.create({ orgSecret })` to create sessions, save each
-   returned session ID alongside the app's own user or order, and return only
-   `verificationUrl` to the frontend. The frontend opens that URL and asks its
-   backend for the final status; a browser redirect alone is not proof of
-   success.
-5. Add a backend callback endpoint. Persist each delivery idempotently, load
-   the expected session ID and org ID from app storage, and call
+3. Reuse a `RECLAIM_ORG_SECRET` the app already has. Otherwise an organization
+   owner calls `issue_org_token`; its `orgSecret` is shown once. Write it with
+   your file tools into the backend's env file (for example
+   `RECLAIM_ORG_SECRET=rorg_…` in `.env`) and make sure that file is
+   gitignored. Keep it out of frontend bundles, logs, source control, and the
+   final response.
+4. Prefer plain HTTP from the backend (see [Code to write](#code-to-write)).
+   Create sessions with `POST /verifications/sessions`
+   (`Authorization: Bearer $RECLAIM_ORG_SECRET`), save each returned session ID
+   alongside the app's own user or order, and return only `verificationUrl` to
+   the frontend. The frontend opens that URL and asks its backend for the final
+   status (`GET /verifications/sessions/{sessionId}`); a browser redirect alone
+   is not proof of success. Use `@reclaimprotocol/client`
+   (`ReclaimVerification.create({ orgSecret })`, `sessions.create`) only when
+   the developer asks for it.
+5. Add a backend callback endpoint. Persist each delivery idempotently and load
+   the expected session ID and org ID from app storage. To verify the result on
+   your callback, install `@reclaimprotocol/client` in the backend and call
    `reclaim.results.receive(body, { reclaimSessionId, expectedAud,
    orgEthPrivateKey })`. Use the verified proof data to update app state.
    Handle callback retries and terminal failure outcomes.
@@ -48,6 +53,100 @@ consumer backend uses the separate organization token. The SDK's API-only
 entry point, `@reclaimprotocol/client/api`, is available when an application
 needs typed Builder operations without the full verification workflow.
 
+The MCP session tools (`create_verification_session`,
+`get_verification_session`, `list_verification_events`,
+`list_verification_deliveries`, `retry_verification_callback`,
+`create_callback_subscription`, `list_callback_subscriptions`,
+`delete_callback_subscription`, `bind_verification_session_tee_nonce`, and
+`get_verification_result`) call these same production endpoints with the org
+key: pass it as `orgToken`, or let them fall back to the MCP server's
+`RECLAIM_ORG_SECRET`. Use them, or `curl` with the key from `.env`, to test the
+integration end to end.
+
+## Code to write
+
+Use the API base URL the developer's Builder runs at (production:
+`https://build.reclaimprotocol.org`). Every call authenticates with
+`authorization: Bearer $RECLAIM_ORG_SECRET`.
+
+Subscribe a callback once (or use `create_org_callback_subscription`). Session
+creation returns 409 while the org has none, and a result is only delivered to
+subscriptions that include the event the session ends with, so subscribe to all
+five:
+
+```bash
+curl -X POST https://build.reclaimprotocol.org/verifications/callback-subscriptions \
+  -H "authorization: Bearer $RECLAIM_ORG_SECRET" \
+  -H "content-type: application/json" \
+  -d '{
+    "callbackUrl": "https://your.app/reclaim/callback",
+    "events": [
+      "verification_success",
+      "verification_rejected",
+      "verification_error",
+      "verification_cancelled",
+      "session_expired"
+    ]
+  }'
+```
+
+Create a session per claimant, from the backend; store `id` and hand
+`verificationUrl` to the frontend:
+
+```bash
+curl -X POST https://build.reclaimprotocol.org/verifications/sessions \
+  -H "authorization: Bearer $RECLAIM_ORG_SECRET" \
+  -H "content-type: application/json" \
+  -d '{
+    "providers": [
+      {
+        "providerId": "<your-provider-id>"
+      }
+    ],
+    "context": {
+      "userId": "abc"
+    }
+  }'
+```
+
+Receive and verify the result on the callback route. This is the one place the
+client package is needed:
+
+```js
+import { ReclaimVerification } from '@reclaimprotocol/client'
+
+const reclaim = ReclaimVerification.create({
+  orgSecret: process.env.RECLAIM_ORG_SECRET,
+})
+
+app.post('/reclaim/callback', async(req, res) => {
+  const outcome = await reclaim.results.receive(req.body, {
+    reclaimSessionId: sessionId, // the id you stored
+  })
+  if(outcome.kind === 'result') {
+    console.log(outcome.result.payload) // verified
+  }
+
+  res.sendStatus(200)
+})
+```
+
+Check or investigate a session, from the backend (optional, e.g. a status
+endpoint the frontend polls) or by hand with `curl`. All take the org key:
+
+| Route | Use |
+| --- | --- |
+| `GET /verifications/sessions/{sessionId}` | Status and outcome. |
+| `GET /verifications/sessions/{sessionId}/events` | The claimant's event timeline, to see where a flow stopped. |
+| `GET /verifications/sessions/{sessionId}/deliveries` | Callback delivery attempts and their responses. |
+| `GET /verifications/sessions/{sessionId}/result` | Recovery only: a signed result Builder hasn't delivered yet. Builder clears it once the callback succeeds, or after 7 days undelivered (`payload: null`). Verify with `verifyResultFull`. |
+| `POST /verifications/sessions/{sessionId}/retry-callback` | Redeliver an undelivered result (within the 7 days). |
+
+```bash
+curl https://build.reclaimprotocol.org/verifications/sessions/$SESSION_ID \
+  -H "authorization: Bearer $RECLAIM_ORG_SECRET"
+```
+
 ## Create and launch a session
 
 Consumers authenticate with an organization token (`rorg_…`, issued in the
@@ -109,7 +208,8 @@ that public key instead; decrypt it with `@reclaimprotocol/client`'s
 `decryptCallback`/`verifyResult` and the org's eth private key before treating
 it as a result. A session created without `canEncryptResult` never needs this
 step. Troubleshoot a stuck or failed session with `get_verification_session`,
-`list_verification_events`, and `list_org_verification_sessions`.
+`list_verification_events`, `list_verification_deliveries` (all with
+`orgToken`), and `list_org_verification_sessions`.
 
 ## Use the browser extension
 

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

@@ -1,5 +1,5 @@
 // AUTO-GENERATED by packages/app/scripts/mcp-tools-gen.ts
-// from packages/app/openapi.yaml (spec v0.1.0, source sha256:9ba46b5cbd7c).
+// from packages/app/openapi.yaml (spec v0.1.0, source sha256:3e28ff308da3).
 // The hash catches drift the version misses (a spec can change without a
 // version bump) — do not remove it as "redundant" with the version.
 // Run `npm run openapi:gen --workspace=packages/app` to regenerate. Do not edit by hand.
@@ -9,7 +9,7 @@ import { toZod } from './to-zod.ts'
 
 export const MCP_TOOLS = {
 	"AddOrgMember": {
-		description: "Invite a member to an organization\n\nOwner only. Invites a user to the organization by email. The invitee does **not** need to be a registered user — an invite is created in either case, and an invite email with an accept link is dispatched. The new row is returned with `status: PENDING`; it flips to `ACTIVE` only when the invitee explicitly accepts via `POST /orgs/{orgId}/invite`. `PERSONAL` organizations reject this call (409).",
+		description: "Invite a member to an organization\n\nOwner only. Invites a user to the organization by email. The invitee does **not** need to be a registered user — an invite is created in either case, and an invite email with an accept link is dispatched. The new row is returned with `status: PENDING`; it flips to `ACTIVE` only when the invitee explicitly accepts via `POST /orgs/{orgId}/invite`.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -50,7 +50,7 @@ export const MCP_TOOLS = {
 						},
 						"role": {
 							"type": "string",
-							"description": "Role a user holds in an organization. `OWNER` can invite, promote, demote, and remove members, and delete the org. `MEMBER` has read/write access to resources owned by the org but cannot manage membership. `PERSONAL` orgs have exactly one `OWNER` and reject all member-mutating operations.",
+							"description": "Role a user holds in an organization. `OWNER` can invite, promote, demote, and remove members, and delete the org. `MEMBER` has read/write access to resources owned by the org but cannot manage membership.",
 							"enum": [
 								"OWNER",
 								"MEMBER"
@@ -425,6 +425,12 @@ export const MCP_TOOLS = {
 							"maxLength": 132
 						}
 					}
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -434,6 +440,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"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.",
@@ -581,6 +588,12 @@ export const MCP_TOOLS = {
 							}
 						}
 					}
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -590,9 +603,10 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"CreateOrg": {
-		description: "Create an organization\n\nCreates a new `ORG`-kind organization with the caller as its first `OWNER`. The personal org is created automatically at user signup and is not created via this endpoint.",
+		description: "Create an organization\n\nCreates a new `ORG`-kind organization with the caller as its first `OWNER`. Every user gets a default organization at sign-up, and it counts toward their org-creation limit (1 active organization unless Reclaim support raises it). Past the limit this returns `409`; contact support@reclaimprotocol.org to raise the limit or archive an organization.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -611,7 +625,7 @@ export const MCP_TOOLS = {
 				"body": {
 					"type": "object",
 					"additionalProperties": false,
-					"description": "Body for `POST /orgs` — just a name. Every org is created keyless, like auto-provisioned personal orgs; its Ethereum (secp256k1) key pair is published separately via `PUT /orgs/{orgId}/keypair`, which is also where `canEncryptResult` is set. Creation deliberately collects nothing else so it never blocks on generating and safeguarding a private key.",
+					"description": "Body for `POST /orgs` — just a name. Every org is created keyless, like each user's default org; its Ethereum (secp256k1) key pair is published separately via `PUT /orgs/{orgId}/keypair`, which is also where `canEncryptResult` is set. Creation deliberately collects nothing else so it never blocks on generating and safeguarding a private key.",
 					"required": [
 						"name"
 					],
@@ -1580,7 +1594,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"CreateVerificationSession": {
-		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 (omitted: the Portal). Billing refusal returns 402 or 429 with event billing_required and a terminal sessionId.",
+		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 (omitted: the Portal). Send the end user to the returned verificationUrl; that is where they verify. Billing refusal returns 402 or 429 with event billing_required and a terminal sessionId.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -1638,9 +1652,16 @@ export const MCP_TOOLS = {
 						},
 						"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 (`portals`) 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.",
+							"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 (`portals`) 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. The built-in clients are `{origin}/share/{name}`, listed in the examples.",
 							"maxLength": 2000,
-							"pattern": "^https?://"
+							"pattern": "^https?://",
+							"examples": [
+								"https://build.reclaimprotocol.org/share/portals",
+								"https://build.reclaimprotocol.org/share/verifier-app",
+								"https://build.reclaimprotocol.org/share/reclaim-browser-extension",
+								"https://build.reclaimprotocol.org/share/builder",
+								"https://build.reclaimprotocol.org/share/inapp-sdk"
+							]
 						},
 						"themeId": {
 							"type": "string",
@@ -1755,6 +1776,12 @@ export const MCP_TOOLS = {
 							}
 						}
 					}
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -1764,6 +1791,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"DecideProviderVersionReview": {
 		description: "Record a decision on a provider version review\n\nApproves or rejects a provider version awaiting review. Admin only. Approval promotes the version to the live channel; rejection moves it to the rejected branch with a reason. Use admin_reviews to find versions waiting on a decision.",
@@ -1853,6 +1881,12 @@ export const MCP_TOOLS = {
 				},
 				"body": {
 					"type": "object"
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -1861,6 +1895,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"DeleteOrgCallbackSubscription": {
 		description: "Delete an organization's callback subscription\n\nRemoves a callback subscription. Caller must be an active member of the owning org.",
@@ -2156,12 +2191,34 @@ export const MCP_TOOLS = {
 							"type": "string",
 							"enum": [
 								"claude",
+								"copilot",
 								"cursor",
+								"omp",
 								"opencode",
 								"codex",
+								"antigravity",
 								"others"
 							]
 						},
+						"providerId": {
+							"type": "array",
+							"maxItems": 20,
+							"items": {
+								"type": "string",
+								"format": "uuid"
+							}
+						},
+						"client": {
+							"type": "string",
+							"enum": [
+								"auto",
+								"portals",
+								"verifier-app",
+								"reclaim-browser-extension",
+								"builder",
+								"inapp-sdk"
+							]
+						},
 						"from": {
 							"type": "string",
 							"maxLength": 40,
@@ -2174,10 +2231,6 @@ export const MCP_TOOLS = {
 							"pattern": "^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2}(\\.\\d+)?)?(Z|[+-]\\d{2}:\\d{2})?)?$",
 							"description": "One end of a date window: either a calendar date (`2026-09-01`, read as UTC midnight) or a full ISO date-time. The date-only form is what a native `<input type=\"date\">` submits, so `format: date-time` alone would reject every filter the dashboard's own form sends."
 						},
-						"providerId": {
-							"type": "string",
-							"format": "uuid"
-						},
 						"verificationClientId": {
 							"type": "string",
 							"minLength": 1,
@@ -2560,6 +2613,12 @@ export const MCP_TOOLS = {
 				},
 				"body": {
 					"type": "object"
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -2568,6 +2627,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"ImportDevtoolsProvider": {
 		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.",
@@ -2695,6 +2755,12 @@ export const MCP_TOOLS = {
 				},
 				"body": {
 					"type": "object"
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -2703,6 +2769,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"ListOrgCallbackSubscriptions": {
 		description: "List an organization's callback subscriptions\n\nReturns every callback subscription owned by the organization. Caller must be an active member of the org.",
@@ -2740,7 +2807,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"ListOrgs": {
-		description: "List organizations the caller belongs to\n\nLists the organizations the caller belongs to, personal and shared. Use it first to find an organization id — most other tools take one.",
+		description: "List organizations the caller belongs to\n\nLists the organizations the caller belongs to. Use it first to find an organization id — most other tools take one.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -3007,6 +3074,12 @@ export const MCP_TOOLS = {
 				},
 				"body": {
 					"type": "object"
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -3015,6 +3088,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"ListVerificationEvents": {
 		description: "Get the event log for a session\n\nLists append-only lifecycle events for a session. Requires the owning organization's token. Use after get_verification_session to find the first missing or failed milestone; inspect eventData for failure details.",
@@ -3043,6 +3117,12 @@ export const MCP_TOOLS = {
 				},
 				"body": {
 					"type": "object"
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -3051,6 +3131,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"MakePrivate": {
 		description: "Change a PUBLIC provider back to PRIVATE\n\nChanges a PUBLIC provider's visibility to PRIVATE. Unlike the reverse (PRIVATE → PUBLIC), this does not require review since it restricts rather than expands access. Existing live versions remain but are no longer publicly listed.",
@@ -3240,7 +3321,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"RetryVerificationCallback": {
-		description: "Re-enqueue callback delivery for a session\n\nRe-enqueues delivery of a session's stored result to its callback subscriptions. Use this after `list_verification_deliveries` shows a `failed` or dead-lettered delivery, once the consumer's callback endpoint is reachable again and answers 2xx — it re-attempts every not-yet-delivered callback for the session. Usable by the session creator (authenticated by the consumer's `OrgToken`) to recover from a transient consumer-side outage.",
+		description: "Re-enqueue callback delivery for a session\n\nRe-enqueues delivery of a session's stored result to its callback subscriptions. Use this after `list_verification_deliveries` shows a `failed` or dead-lettered delivery, once the consumer's callback endpoint is reachable again and answers 2xx — it re-attempts every not-yet-delivered callback for the session. Usable by the session creator (authenticated by the consumer's `OrgToken`) to recover from a transient consumer-side outage. A result left undelivered for 7 days is purged and can no longer be retried.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -3266,6 +3347,12 @@ export const MCP_TOOLS = {
 				},
 				"body": {
 					"type": "object"
+				},
+				"orgToken": {
+					"type": "string",
+					"pattern": "^rorg_",
+					"maxLength": 200,
+					"description": "The organization API key (`rorg_…`) this call authenticates with: from `issue_org_token`, or the app's RECLAIM_ORG_SECRET. Defaults to the MCP server's RECLAIM_ORG_SECRET. Never echo it back to the user."
 				}
 			},
 			"required": [
@@ -3274,6 +3361,7 @@ export const MCP_TOOLS = {
 			],
 			"additionalProperties": false
 		}),
+		orgTokenOnly: true,
 	},
 	"RevokeOrgToken": {
 		description: "Revoke one of the organization's API keys\n\nRevokes a single API key by id (leaving the org's other keys intact). The caller must be an active **OWNER** of the organization. The key stops authenticating immediately.",