Home / MCP registry index / com.coveragecat/insurance
Coverage Cat
com.coveragecat/insurance in the official MCP registry.
Endpoint https://www.coveragecat.com/api/consumer/mcp.
The registry describes it as: Get umbrella and homeowners insurance quotes, select a policy, and bind coverage.
We read its 23 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
umbrella_consumer_prefill homeowners_consumer_prefill consumer_intake_issues consumer_intake_patch umbrella_consumer_select umbrella_consumer_bind umbrella_consumer_attach umbrella_consumer_payment umbrella_consumer_policy umbrella_consumer_service homeowners_consumer_select homeowners_consumer_bind homeowners_consumer_policy homeowners_consumer_service home_calculator umbrella_calculator auto_estimates collision_and_comprehensive_coverage file_a_claim homeowners_agent_finder docs_list_topics docs_search docs_get_resource
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-coveragecat-insurance)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.