For developers
Public API and MCP server
Everything public on this site is available as JSON, read-only, with no key. And the registry is itself an MCP server: point an AI client at it and ask for the server you need.
The registry as an MCP server
Streamable HTTP, stateless, no authentication. Add it to Claude, Cursor or any MCP client as a remote server and ask something like “find me an MCP for loss runs”.
Endpoint
https://insurancemcps.com/mcp
Claude Desktop / Claude Code
{
"mcpServers": {
"insurancemcps": {
"type": "http",
"url": "https://insurancemcps.com/mcp"
}
}
}Claude Code: claude mcp add --transport http insurancemcps https://insurancemcps.com/mcp
Tools
search_servers
Search the registry of published insurance MCP servers. Filter by free text, category, integration, audience, trust tier, auth or hosting. Returns public listings with their tools, data-handling statement and trust tier.
Arguments: query, category, integration, audience, tier, auth, hosting, sort, page, pageSize
get_server
A published listing by slug, with its official server.json when the builder supplied one and its Council scorecard when one is published.
Arguments: slug
list_categories
Every category in the registry (rating, claims, policy admin, …) with how many published servers each holds.
list_integrations
Every system servers integrate with (agency management systems, carrier platforms, …) with how many published servers list each.
list_audiences
Who a server is for (agencies, carriers, MGAs, …) with how many published servers name each.
list_lab_ideas
Public, open ideas in the Idea Lab — what the industry is asking to have built — with votes, backers and stage. Nothing about who posted or voted.
Arguments: query, stage, sort, page, pageSize
get_lab_idea
A public, open idea by slug, with its full brief, stage, checklist and vote counts.
Arguments: slug
Every tool is read-only and returns the same data as the JSON API below, as text and as structuredContent. The server’s own server.json is at /api/v1.
{
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
"name": "com.insurancemcps/registry",
"description": "Search the neutral registry of insurance MCP servers, their trust tiers and Council scorecards, and the Idea Lab.",
"version": "1.0.0",
"websiteUrl": "https://insurancemcps.com/",
"remotes": [
{
"type": "streamable-http",
"url": "https://insurancemcps.com/mcp"
}
]
}JSON API
Base URL https://insurancemcps.com/api/v1. All endpoints are GET, answer JSON, allow any origin (CORS *) and need no key. Lists come back as { items, total, page, pageSize }; errors as { error: { code, message } }.
| Endpoint | Returns |
|---|---|
| /api/v1/servers | Published servers, paged. Filters: q, category, integration, audience, tier, auth, hosting, sort (relevance | trust), page, pageSize (≤ 100). |
| /api/v1/servers?format=server.json | The same search in the official MCP Registry list shape: each entry is the listing’s server.json under `server`, with the registry’s slug, URL and trust tier under `_meta["com.insurancemcps"]`. Only listings that carry a server.json appear. |
| /api/v1/servers/{slug} | One published listing (`server`) and its Council scorecard (`scorecard`, or null). |
| /api/v1/categories | Categories with the number of published servers in each. |
| /api/v1/integrations | Systems servers connect to, with counts. |
| /api/v1/audiences | Who servers are for, with counts. |
| /api/v1/ideas | Public, open Idea Lab ideas. Filters: q, stage, sort (hot | newest | closest | votes), page, pageSize. |
| /api/v1/ideas/{slug} | One public idea with its brief, stage, checklist and vote counts. |
curl "https://insurancemcps.com/api/v1/servers?q=loss%20runs&tier=verified"
Limits and what is never included
- 120 requests per minute per address, across the API and
/mcptogether. Past that you get429withRetry-After; every reply carriesX-RateLimit-*headers. - Only published listings and public, open ideas. Drafts, pending, rejected and delisted listings and private ideas do not exist as far as the API is concerned.
- No maintainer, submitter, voter or backer identities, no emails, no moderation notes. Council reviewers appear as they chose to on the site: a name or a verified alias, never an email.
- The trust tier and scorecard are facts about the listing. Nobody pays for either; see stewardship.