Verisk Underwriting Intelligence

Limits

• ISO loss costs are advisory projections, not prices, and Verisk says so in its own words. Verisk describes ISO's advisory prospective loss costs as using historical data and its analyses "to project average future claim costs and loss adjustment expenses". Those two components are what a loss cost contains. Verisk positions them as "a better benchmark" that "can help insurers develop more accurate pricing", and lists among the benefits that ISO's information combined with an insurer's own data can help "calculate the rates you need to reach your profit targets" — which is a statement that the rate is the insurer's to calculate, not ISO's to supply. An agent will render a loss cost as a number, and a number looks like a price. It is not one.
• The material is filed with state regulators, and Verisk names that as part of the value. Verisk states that "ISO loss costs are submitted to state regulators for review", and describes submitting forms and loss costs to state regulators on behalf of insurers as a service of Core Lines. This connector therefore reaches material that sits inside a regulatory process. Nothing on Verisk's connector page suggests the connector participates in that process, and Verisk states the opposite about writes — see the next point.
• Verisk places accountability with the professional, explicitly. Its launch announcement states that judgment and accountability "remain with insurance professionals, consistent with existing processes and controls", and separately that "accountability remains with people". Its CEO is quoted saying data must be authoritative and decisions explainable. Read those as the vendor's own framing of what the connector is for and what it is not.
• The tools are read-only, per Verisk and per Anthropic, and we could not verify it at the annotation level. Verisk states the connector "retrieves data" and "cannot file circulars, edit indications, or push anything back to ISO". Anthropic's directory label is the exact string "Read only". Because the endpoint refuses anonymous connections we never read a readOnlyHint or destructiveHint annotation for any of the four tools, so no tool on this server is annotated in any source we can see. The claim is documentary, not observed.
• Coverage is bounded by your subscription, and by what each tool tracks. Verisk states data is limited to the products and datasets covered by your current subscription, and that the tools correspond to the information in traditional ISO data tools. The Indications tool tracks an ongoing rollout of the new Indications Center, so its coverage is expanding rather than complete. A thin answer can mean thin entitlement or thin rollout.
• Pagination is the reader's problem, by Verisk's own account. Verisk documents that some queries span many pages, tells users to let Claude fetch them rather than interrupting, and gives "Claude returns partial results" its own troubleshooting row with the suggested remedy of asking Claude to verify it fetched all pages. A partial answer that looks complete is the failure mode that follows from that, and Verisk names it.
• One of the four tools puts vendor-authored material into the conversation. Covered in full above. Verisk documents that iso_visualizer_skill_include is auto-included and renders ISO information; it does not publish what the included skill says. Unverified.
• No public ISO Core Lines terms of use exist that we could find, so the AI-use position sits in your contract. Verisk's public legal pages are a website conditions-of-use document, an SMS terms document, and the Xactware EULA — its full en-US sitemap lists no others. The website conditions govern verisk.com itself and carry an "AS IS" warranty disclaimer plus a bar on data mining and robots against the *site*; they say nothing about ISO data licensing. The Xactware EULA does carry a broad AI prohibition — it bars using artificial intelligence, machine learning, large language models and similar tools on the Services except where expressly authorised as an "Authorized AI Use" — but Xactware Solutions, Inc. is a different Verisk business, the one behind the XactRestore connector, and that EULA is not the ISO Core Lines agreement. We are recording the shape, not asserting it applies here. What Verisk does say publicly about this connector is that its use of AI is "within established, controlled workflows and aligned with its contractual data use, confidentiality, and governance obligations". Verisk shipping the connector is strong evidence the route is authorised for subscribers; your governing terms are the subscription agreement, and we cannot read it. Confirm with your Verisk representative. We are describing a documentation gap, not giving legal advice.
• We never authenticated and never called a tool. Everything above about tool behaviour comes from Verisk's documentation and Anthropic's directory. We probed the endpoint once anonymously to establish the auth posture and read the public discovery documents. No credentials were supplied.
• This page gives no insurance, actuarial or financial advice. It describes what the tools return and what Verisk says about that material. How loss cost output is used in pricing, filing or reserving is a question for a qualified actuary and your regulator, not for a connector catalogue.

Frequently asked questions

Sources

• Verisk, Verisk Underwriting Intelligence Connector for Claude — https://www.verisk.com/resources/verisk-underwriting-intelligence/ (fetched 2026-08-19; the directory's documentation URL. Despite sitting on Verisk's marketing site it is a genuine connector guide: source of the four tool descriptions and wire names, the Visualizer auto-inclusion statement, the Enterprise-plan and ISOnet entitlement requirements, the MFA and popup requirements, the connection steps, the per-tool permission statement, the read-only limitation, the Experience Index confirmation behaviour, the refresh cadences, the troubleshooting table and the three-question FAQ) · retrieved 2026-08-19
• Verisk, ISO's Advisory Prospective Loss Costs product sheet — https://www.verisk.com/4a2314/siteassets/media/downloads/iso/isos-advisory-perspective-loss-costs.pdf (fetched 2026-08-19; source of the "project average future claim costs and loss adjustment expenses" characterisation, the benchmark framing, the "calculate the rates you need to reach your profit targets" line, and the statement that loss costs are submitted to state regulators for review) · retrieved 2026-08-19
• Verisk, The not-so-secret sauce of ISO Loss Costs — https://www.verisk.com/blog/the-not-so-secret-sauce-of-iso-loss-costs/ (fetched 2026-08-19; describes the four modelling components behind a loss cost — loss development, loss-adjustment expenses, loss cost trends and external factors — and confirms loss costs are estimates rather than prices) · retrieved 2026-08-19
• Verisk, ISO Forms, Rules, and Loss Costs — https://www.verisk.com/products/forms-rules-and-loss-costs/ (fetched 2026-08-19; source of the 31 lines of business figure for Core Lines Services and the statement that Verisk submits forms and loss costs to state regulators on behalf of insurers) · retrieved 2026-08-19
• Verisk newsroom, Verisk Brings Its Trusted Analytics and Generative AI Capabilities Directly into Anthropic's Claude — https://www.verisk.com/company/newsroom/verisk-brings-its-trusted-analytics-and-generative-ai-capabilities-directly-into-anthropics-claude/ (fetched 2026-08-19; 5 May 2026 launch, names Verisk XactRestore as the sibling connector, source of the accountability statements and the contractual-data-use framing of Verisk's AI position) · retrieved 2026-08-19
• Verisk, Verisk XactRestore Connector for Claude — https://www.verisk.com/resources/verisk-xactrestore-connector-for-claude/ (fetched 2026-08-19; confirms the sibling connector exists as a documented product. It publishes no endpoint, and we probed no undocumented path on the gateway host) · retrieved 2026-08-19
• Verisk Analytics Website Conditions of Use — https://www.verisk.com/privacy-policies/verisk-analytics-website-conditions-of-use/ (fetched 2026-08-19; governs verisk.com itself, carries the "AS IS" disclaimer and a data-mining bar against the site, and contains no AI, MCP or ISO data licensing language) · retrieved 2026-08-19
• Xactware EULA — https://www.verisk.com/privacy-policies/xactware-eula/ (fetched 2026-08-19, updated 22 April 2026; source of the "Authorized AI Use" clause. Governs Xactware Solutions, Inc., a different Verisk business — cited to show the shape of Verisk's AI terms elsewhere, not applied to ISO Core Lines) · retrieved 2026-08-19
• Live anonymous probe — 2026-08-19: a single anonymous initialize POST to the endpoint returned HTTP 401 with www-authenticate: Bearer realm="sso.verisk.com", error="invalid_token" and no resource_metadata URL. Response headers name Kong 3.13 and Imperva. No credentials were supplied and no tool was invoked · retrieved 2026-08-19
• Live RFC 9728 probes, all three path forms — https://gatewaymcp.verisk.com/.well-known/oauth-protected-resource (fetched 2026-08-19; 200 with a 122-byte placeholder document, no scopes_supported), the path-append form under /underwriting/intelligencemcp/v1 (byte-identical body, same SHA-1), and the path-insert form (401) · retrieved 2026-08-19
• Live RFC 8414 probes — https://gatewaymcp.verisk.com/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer, endpoints, PKCE and the four generic scopes), the path-append form returning a 28KB Angular SPA login shell, and https://sso.verisk.com/oauth2/ausce3eyr3v1mce0o2p7/.well-known/oauth-authorization-server plus https://sso.verisk.com/.well-known/oauth-authorization-server (both fetched 2026-08-19; Okta tenant documents advertising Okta platform scopes unrelated to this connector) · retrieved 2026-08-19
• verisk.com/robots.txt and sitemap.en-US.xml (fetched 2026-08-19; robots.txt allows all crawlers with six disallowed asset paths and no Content-Signal line, and lists five locale sitemaps. Every Verisk URL above was located through the sitemap or through search rather than guessed. verisk.com/llms.txt returns 404 as an HTML error page, and the .md suffix form of the connector page returns 404) · retrieved 2026-08-19
• Anthropic connector directory — https://claude.ai/directory/5268a4af-f0f3-4b6c-a3ad-2833920399aa (snapshot 2026-08-16; source of the four tool names, the exact "Read only" permissions string, the partner tier, the empty prompt list, the streamable-http transport, the endpoint, the financial-services category, and the description naming the ISO Core Lines Services subscription requirement) · retrieved 2026-08-16
• Verisk support contact — https://www.verisk.com/company/contact/ and privacy policies — https://www.verisk.com/privacy-policies/ (per the directory snapshot, 2026-08-16) · retrieved 2026-08-16