InsurEco weekly roundup: week of 2026-09-28

The week of 2026-09-28 brought two published posts, one on how insurance might organise the growing number of MCP servers and one on the AI risks agents face from tools their clients already use. Across the products, the team also updated the documentation that partners, carriers and agencies rely on to connect with InsurEco.

Published this week

Why insurance needs a neutral registry of MCP servers

Carriers, agencies and builders are starting to connect AI tools to insurance systems through MCP servers, but there is no shared place to find them or judge them. This InsurEco post sets out a proposed answer, insurancemcps.com: a neutral industry registry with InsurEco as steward, Idea Lab voting, AI Council reviews and trust tiers. It matters for anyone deciding which connections to trust as AI tools move closer to policy and claims data. Read the post.

What Insurance Agents Should Fear About AI in 2026 (It's Not the Robots)

From PolicyOS, this post argues that the AI risk most agents miss is not replacement. It is the AI their clients already use: PDF readers and e-signature tools now summarise a quote before the agent can. The post walks through five risks and what to do about each, which makes it a practical read for agencies reviewing how their documents are presented. Read the post.

What shipped across InsurEco

PolicyPay

The PolicyPay integration guide for Sign and Pay was updated for a distribution partner. It now answers four items that were left open after an August walkthrough: the signature flow, templates, outbound webhook events and split pay. It also lists what is not yet available, so partners can plan around current scope.

Separately, PolicyPay published an updated playbook and index for onboarding the next distribution partner on PolicyPay and Split Pay. It describes the onboarding procedure as of 29 September and gathers the existing runbooks, guides and scripts in one place. For new partners, this should mean a more consistent setup.

RaterSpot

The partner packet for a general liability program partner was brought up to date. The kit is built, the API documentation is versioned, an older PDF has been retired, and the partner docs now use polling rather than an approval webhook. Partners working from earlier material should refer to the current packet.

The team also began documenting how changes to the RaterSpot web application are built and rolled out to production. This is a first draft and has not yet been verified against a live deployment.

Jefferson

Ask Jefferson can now be turned on inside RaterSpot for an agency without sending invites. The procedure was used for four agencies on 30 September, with a dry run recommended before each change.

Jefferson also started a plain-English series. The first page explains how Jefferson triages mail: simple sorters remove obvious junk, Claude reads the envelope details of what remains, and the user decides on anything flagged as possibly needing them.

A new guide covers the JCI Index, a single page listing every Jefferson document, including guides, technical write-ups, plans, sales material and public sites. The guide explains the cards, the status badges and how to ask Jefferson to refresh the index.

Tawa

The list of outbound IP addresses that partners and carriers allowlist for Tawa services was corrected so that it shows the dedicated carrier address. Partners and carriers who allowlist Tawa traffic should confirm their configuration matches the current list.

Where to read more

Both published posts are linked above. InsurEco News will report next week's posts and updates in the next roundup.