Model Context Protocol

Verisk Underwriting Intelligence Connector for Claude

Bring ISO loss cost intelligence directly into your Claude conversations. Ask plain-language questions about filings, indications, and experience trends — and get answers grounded in Verisk’s robust actuarial data.

What is this connector?

The Verisk Underwriting Intelligence connector lets Claude pull current data from ISO's loss cost system through the Model Context Protocol (MCP).

Loss Cost Activity

Recent history of filed ISO loss cost changes and summaries of their impact.

ISO Experience Index

Loss experience trends, pure premium movement, and data that drives future indications.

Indications Center

Key details from recent ISO loss cost reviews, including advance preliminary indications. Uncover the why behind our changes.

Visualizer

Helps Claude visualize and render the ISO information.

Ask Claude questions like “Compare the history of GL loss cost changes between Florida and Georgia.” and get a synthesized answer with the underlying data.

Who is this for?

Actuaries

Compare indicated vs. selected, ISO trend selections, and other key data components.

Product Managers

Quickly find the status and impact of ISO loss cost filings along with other relevant information.

Underwriters & Pricing Analysts

Gain context, clarity, and narrative understanding of loss cost trends.

State Filing Teams

Help prepare support based on ISO's filed content.

Verisk Underwriting Intelligence Connector in Claude

Access integrated actuarial views that include loss costs, filing, and market data with Claude Enterprise.

Learn more

Verisk Underwriting Intelligence Connector in Claude

What do I need to get started?

Claude plan

Claude Pro, Team, or Enterprise. Custom connectors are not available on the free tier.

Verisk account

An active Verisk / ISOnet account with entitlements to the ISO loss cost products you want to query (Loss Cost Activity, Experience Index, Indications Center). If you can't access these on ISOnet today, you won't be able to query them through Claude.

MFA

Multi-factor authentication is required by Verisk. Have your authenticator app or registered device ready when you connect.

Browser

A modern browser (Chrome, Edge, Safari, Firefox — current versions). The OAuth handoff opens in a popup, so allow popups for claude.ai.

Network access

Your network must allow outbound traffic to claude.ai and Verisk's authentication endpoints. If you're on a corporate VPN that blocks third-party OAuth flows, contact your IT team.

Admin approval

On Team and Enterprise plans, a workspace admin may need to enable the connector before individual users can connect.

You don’t need:

A separate API key
Authentication is handled through OAuth.

Any local installation
The connector runs server-side; nothing installs on your machine.

Developer access
This is configured by an admin once, then available to entitled users.

Connecting to Claude

Open the connector directory
In Claude, go to Settings → Connectors. On Team and Enterprise plans this may be under Settings → Integrations depending on your workspace configuration.
Find Verisk Underwriting Intelligence
Search for Verisk Underwriting Intelligence. If you don't see it listed:
- On Pro: the connector should appear in the public directory. Try refreshing.
- On Team/Enterprise: an admin needs to enable it for the workspace first. Ask your Claude admin to add it.
Click Connect
You'll be redirected to Verisk's sign-in page in a new window or popup.
Sign in to Verisk
Enter your Verisk username and password, then complete MFA when prompted. This is the same flow you use for ISOnet — Claude does not see or store your password. Afterwards, you'll be returned to Claude.
Tool permissions
Under the Verisk Underwriting Intelligence connector, permissions are configured per tool. Set the appropriate permission level for each tool based on your preference.
Confirm the connection
Start a new chat and ask "What Verisk tools do you have access to?" — Claude should list the tools.

Authentication & security

How authentication works
The connector uses OAuth 2.0. When you click Connect, Claude redirects you to Verisk's identity provider, you sign in there (with MFA), and Verisk returns a scoped access token to Claude. Claude uses that token to call the connector's tools on your behalf.
Anthropic never sees your Verisk password
The sign-in happens entirely on Verisk's domain. Only the resulting token reaches Claude.
Tokens are scoped and time-limited
The access token only grants the read permissions you approved during sign-in. Refresh happens automatically in the background; if your session expires, Claude will prompt you to reconnect.
Permissions follow your Verisk account
The connector inherits your existing Verisk entitlements. If you don't have access to a particular LOB and jurisdictions on ISOnet, you won't see it through Claude either.
Disconnecting
Go to Settings → Connectors → Verisk Underwriting Intelligence → Disconnect at any time. This revokes the token immediately.
Audit & data handling
Queries you run through the connector are processed within your Claude session per Anthropic's standard data policies. Verisk does not store or retain your prompts.

What tools are available?

Four tools power the connector. You don’t need to reference them directly – ask in plain English and Claude can decide which can help.

Loss Cost Activity

Recent history of filed ISO loss cost changes and summaries of their impact.

iso_losscost_activity_get

Sample prompt

What have ISO GL loss cost changes been in California over the past five years?

^{For current-review drivers and the latest indication, the Indications Center tool is more appropriate. Use Loss Cost Activity for history and trends.}

ISO Experience Index

Loss experience trends, pure premium movement, and data that drives future indications.

iso_losscost_experienceindex_get

Sample prompt

Are BOP Business Personal Property losses trending upward in Texas?

^{This tool will ask you to confirm two things before answering: which segments you want and which rolling period (1/2/3/5 yr). That's by design — the index is too large to query unfiltered.}

Indications Center

Uncover the why behind our changes.

Key details from ISO's loss cost reviews: indicated and selected changes by major coverage, class, and territory segments, plus trend selections and other key data components driving the review results.

iso_losscost_indications_get

Sample prompt

Show the most recent loss cost indication summary for Businessowners Policy in Texas.

Visualizer

A helper that runs alongside the loss-cost data tools.

iso_visualizer_skill_include

You don't call it directly — Claude includes it automatically when it pulls ISO data so charts and tables render in minimal format.

Sample prompts

Copy any of these into Claude after connecting.

“What are ISO’s latest loss cost indications for BOP in New Jersey?”

“Show me the experience trends for Businessowners in TN.”

“How do the latest ISO loss cost indications for GL in Arizona compare to the recent history of filed changes?”

Tips for getting better answers

Be specific about state and LOB

"Show me filings" is too broad. "Show me GL filings in TX since 2023" returns a focused answer in one pass.

Let Claude paginate

Some queries span many pages. Claude will fetch them — give it a moment rather than interrupting.

Use follow-ups

Start broad, then drill in. "Show me all 2024 BOP filings in NJ" → "Now break down the largest one by coverage" → "How does that compare to the prior NJ filing?"

Ask Claude to show its work

"Walk me through how you got there" surfaces the data Claude pulled and the reasoning, which can be useful for review and audit.

Limitations and things to know

Tools are read-only.
The connector retrieves data. It cannot file circulars, edit indications, or push anything back to ISO.
Available data is limited to your subscription.
Data is limited to the products and datasets covered by your current subscription.
Claude may ask clarifying questions.
Claude may confirm segments and rolling period before querying. This is intentional and produces better answers.

Troubleshooting

Symptom	Try this
Verisk Underwriting Intelligence doesn't appear in the connector directory	On Team/Enterprise, ask your Claude admin to enable it. On Pro, refresh the page.
OAuth popup doesn't open	Allow popups for claude.ai in your browser, then click Connect again.
Stuck on the Verisk sign-in page	Confirm your ISOnet login works at verisk.com. If MFA is failing, re-enroll your device in Verisk first.
"Access denied" after signing in	Your Verisk account doesn't have entitlements for the ISO products. Contact your Verisk administrator to provision access.
Connection succeeds but no tools are listed	Start a fresh chat. If still missing, disconnect and reconnect from Settings → Connectors.
"Authentication expired" or 401 errors	Your token expired. Open Settings → Connectors, click Verisk Underwriting Intelligence, and re-authenticate.
Claude returns partial results	Try asking: "Did you fetch all pages? Please verify."
Answers don't seem to include recent data or don't go back in time enough	The tools correspond to the information in traditional ISO data tools on core.verisk.com. For the Indications tool, it corresponds to the ongoing rollout of the new Indications Center tool. The Loss Cost Activity tool includes several recent years of information. The ISO Experience Index is updated about once per quarter with new experience.
Claude picks the wrong tool	Be explicit: "Use the Indications Center to answer this" or "Pull this from the loss cost filing history."

Frequently asked questions

Do I need to know the tool names to use this?

No. Ask in plain English and Claude will determine the best tool to answer the question.

Will Claude make up filing data if it can't find it?

Claude is instructed to return only what the tools provide and flag missing states. If something seems off, ask "Where did this come from?" and Claude will cite the source.

Can I export results?

Yes — ask Claude to format results as a table, CSV, or Excel file and it will produce a downloadable file.

Feedback

We would like to hear feedback from our users as we enhance this new experience and plan new capabilities.

If you have questions or comments, please contact your Verisk representative.