Verisk XactRestore MCP server icon

Verisk XactRestore

by Verisk XactRestore

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Finance18 tools

Build and refine property restoration estimates in XactRestore from an AI agent. Anthropic lists 18 tools — 10 read, 8 write, including 2 that archive. OAuth via Verisk Identity with identity-only scopes, and a mandatory XactAI licence.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Verisk XactRestore via MCP

https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Verisk XactRestore Tools & Capabilities (18)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Archiving a room or a line item is not covered by Verisk's documented recovery path. Verisk states deleted projects can be restored for up to one year, and states equally clearly that individual rooms, groups and line items cannot be recovered separately. The two archive tools act at exactly that finer granularity. This is the sharpest edge on the connector, and the vendor does not connect these two facts anywhere — we did.
  • We counter-recommend Verisk's "Always allow" guidance for the two archive tools. The recommendation appears in both Verisk's setup article and its resource page, and it is sound for the read and pricing tools. Applied to ArchiveEstimateRoomsOrAreas and ArchiveConstructionEstimateLineItems it removes the last confirmation in front of an unrecoverable action.
  • No application scopes exist. The resource descriptor declares openid, profile and offline_access; the authentication challenge advertises openid offline_access. Nothing at the OAuth grant separates reading a price from archiving a line item. Notably, Verisk's Okta authorization server advertises broader scopes including rw_api and property-claims:full, but the resource-specific descriptor does not offer them, so they are not part of this connector's grant. A reader comparing the two documents will see the discrepancy; the narrower one governs.
  • Verisk publishes no text enumeration of the tools. The only vendor list is a partial screenshot. Ten of the 18 names are attested by Anthropic alone, so a silent rename among them would be undetectable from outside.
  • We could not read tool schemas, safety annotations, prompts or resources. The endpoint returned 401 to initialize, tools/list, prompts/list and resources/list. The directory names six prompts, but we could not confirm the prompts capability is declared, so we report the names as the directory's claim rather than an observed surface.
  • The vendor's own documentation URL is behind a login wall. The directory nominates a Salesforce Experience Cloud article that JavaScript-redirects every visitor to a Verisk Identity SSO page and yields 33 words of shell markup. The readable copy of the same article — number 2622 — is on a public host, linked below.
  • Whether job records return loss photographs or contact details is unresolved. Schemas are unreadable and we did not test. XactRestore holds photos and documents at the product level; whether this connector surfaces them is unknown rather than ruled out.
  • The carrier-facing gap is temporary by Verisk's own statement. Verisk plans XactRestore to Xactimate estimate transfer "in the near future". When that ships, the no-submission finding on this page needs re-checking.
  • No cost or metering information is published. No tool name carries a credit, balance, usage, quota or billing verb, so nothing in the surface could report spend. Access is gated by subscription and an XactAI licence rather than metered per call, as far as Verisk documents.

Frequently asked questions

No. Nothing in the 18 tools transmits an estimate anywhere. The surface builds estimates inside XactRestore only. Verisk's own documentation states you cannot produce the estimate in Xactimate — its carrier-facing product — and that transferring estimates from XactRestore to Xactimate is planned for the future, not shipped. The insurer-facing step stays manual.

Eight of the 18 tools write. They create projects, create, update and duplicate rooms, and add and update line items. Two of the eight archive: one removes rooms or areas, the other removes line items from an estimate. No tool deletes a project outright. Archiving is the most consequential action the surface offers.

Not through the deleted-projects feature. Verisk documents a one-year recovery window for whole deleted projects, and states explicitly that individual rooms, groups and line items cannot be recovered separately. So the two archive tools act on exactly the objects Verisk's documented recovery path does not cover. Treat both as effectively irreversible.

Identity claims and a refresh token, nothing more. The server's RFC 9728 descriptor declared openid, profile and offline_access on 2026-08-23, and its authentication challenge advertised openid and offline_access. Verisk's own consent screenshot shows only Personal Information and Offline Access. No scope separates reading a price from archiving a line item.

Yes, indirectly but really. Projects in XactRestore are jobs at named properties, and Verisk's sample prompt in its own documentation names a homeowner and a loss type. Project search and detail tools return whatever the job record holds. Verisk states it does not receive, store or retain your prompts, which is a separate matter from what the tools return.

Three things. Verisk requires an active XactRemodel or XactRestore subscription, an XactAI licence assigned to your user, and a Claude account supporting MCP connectors. Verisk stresses the XactAI licence must be assigned to your specific user, not merely owned by the organisation. Any Claude plan works, and multi-factor authentication is mandatory.

Only as a screenshot, and only partially. Verisk's setup article shows Claude's tool-permission panel with the counter reading 18, matching Anthropic's count exactly. Eight names are legible before the list scrolls out of frame, and all eight match the directory once case conventions are normalised. No text enumeration exists anywhere.

For convenience, and it removes your only per-action checkpoint. Verisk's article states it is recommended to set all tools to Always allow, and its resource page recommends enabling all tools. Eight of the 18 write and two of those archive. Blanket approval means an archive runs without a prompt, so consider approving the archive tools individually.

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Finance
Developer
Verisk XactRestore
Tools
18
Domain
xactrestore-xactremodelserver-usw2-prod.propsol.io

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.