Skip to content
insurancemcps

For developers

List your server

The registry is neutral: every server is listed on the same terms, ranked by relevance or trust, never by who paid. Here is how a listing gets in and how it earns its tier.

Submit a server

  1. Step 1

    Submit

    Paste a server.json or fill the form: what it does, its tools, how it authenticates, where it runs, what it does with data, and where it belongs.

  2. Step 2

    Moderation

    A steward checks that it is a real MCP server for insurance work and that the listing says what it needs to. They approve, ask for changes, or explain why not. You get an email at each step.

  3. Step 3

    Listed

    Approved servers go live at the Listed tier. Edit the listing any time from your listings page; it stays live while you do.

  4. Step 4

    Earn trust

    Verified means a steward confirmed the server runs and matches its listing. Council Reviewed means an independent three-seat panel scored it. Neither can be bought.

What each trust tier means

Listed

Submitted and approved by a steward. The auth, hosting and data-handling facts are as stated by the builder and have not been checked.

Verified

A steward confirmed the server exists, runs, and matches its listing. If you later change auth, hosting or data handling, the listing drops back to Listed until it is re-checked — the badge always describes the current facts.

Council Reviewed

An independent Council panel — a practitioner, a compliance and security expert, and an AI engineer — reviewed it and published a scorecard tied to a version.

Nobody pays for a tier, a badge or placement. The stewardship rules are public.

Already listed? Claim it

Founding and imported listings have no maintainer yet. If one is yours, open its page and choose Claim this listing. You get a one-time token; prove control of the repository by either:

  • committing a file named insurancemcps-claim.txt containing the token to the default branch, or
  • pushing a tag named insurancemcps-claim-<token>.

Listings imported from the official MCP Registry are proven against the repository their io.github.* namespace names. Once verified, you maintain the listing: edit it, and it is yours in the registry.

Build on the registry

Everything public here is a read-only JSON API, and the registry is itself an MCP server your AI client can search. API and MCP documentation.

Invite-only while the doors open

New submissions are currently limited to invited builders and existing maintainers. If you build insurance MCP servers and want in, ask a steward.

For developers · insurancemcps