Home / MCP registry index / io.tooloracle/insuranceoracle

io.tooloracle/insuranceoracle

io.tooloracle/insuranceoracle in the official MCP registry. Endpoint https://tooloracle.io/insurance/mcp/. Source: github.com/ToolOracle/insuranceoracle.

The registry describes it as: InsuranceOracle - 12 insurance compliance tools: GDV, BaFin VAG, Solvency II, IDD.

We read its 12 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.

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

insurance_company insurance_news natcat_live earthquake_risk weather_risk natcat_history solvency_check insurance_regulation risk_score insurance_glossary claim_news health_check

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-tooloracle-insuranceoracle/badge.svg)](https://lazaretto.dev/mcp-registry/io-tooloracle-insuranceoracle)

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.