Openinsurance Wiki MCP server
io.github.sluyasu/openinsurance-wiki·v0.2.0·2 starsOpen, source-cited knowledge base of Belgian insurance products: search, compare, verify, overlaps.
2 stars15 downloads/wk
Reviews
Write oneNobody has reviewed Openinsurance Wiki yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Openinsurance Wiki tools (10)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
compare_productsCompare 2+ products side by side on one dimension: coverages | exclusions | deductibles. Each name is matched case-insensitively against extracted product names; pass insurer_slugs (same length/order as product_names) to pin each name to one insurer. A name matching several DISTINCT products is refused with the candidates listed (refine it rather than let the server guess). For each resolved name
find_overlapFlag CANDIDATE duplicate cover when combining 2+ products (e.g. a home policy + a family-liability policy). Each product's coverages (or exclusions) are tagged with a controlled category (schema/coverage_categories.json); a candidate overlap is a category present in 2+ of the products. Deterministic + heuristic: it surfaces likely duplicates for an agent to confirm against the actual descriptions.
get_branch_overviewReturn the hand-authored overview page for a branch (by slug or label).
get_coverageCompact, question-oriented view of ONE product: only the coverages and exclusions relevant to `topic` (e.g. 'vol', 'degats des eaux', 'ski hors-piste'), with their limits, deductibles, verbatim quotes and page numbers. Prefer this over get_product when answering a specific guarantee question: everything needed to quote is in the response and nothing else. Matching is accent- and case-insensitive o
get_pageReturn the full text of one knowledge page by its repo-relative path (from search results). Text files in the knowledge folders only (.md, .json, .yml, .yaml, .txt, .csv).
get_productReturn a product's structured data (coverages, exclusions, deductibles, etc.) as JSON, plus its source_url. `product_name` is matched case-insensitively (substring). Optional filters: document_type (conditions_generales | ipid | conditions_particulieres | conditions_tarifaires) and edition (substring of the edition_date, e.g. '2026'). When one product has several documents (e.g. its CG and its IPI
list_branchesList insurance branches for a country with their labels, mandatory flag and product counts.
list_countriesList countries covered: product/insurer/regulation counts, how many branches have at least one product (branches_covered), the size of the country's branch taxonomy (branch_taxonomy), and how many hand-written branch overview pages exist (branch_overview_pages).
searchSearch wiki pages by title/branch/insurer and page content. Filter by type (product|branch|insurer|regulation|concept|moc), branch slug, insurer slug. Returns matches with path, source_url and freshness; when more than `limit` pages match, the response says how many were left out.
verify_claimVerbatim evidence check for ONE factual claim about a product ('le ski hors-piste est couvert avec un moniteur', 'franchise de 250 EUR en vol'). Returns the document excerpts (coverages, exclusions, quotes, definitions, deductibles, summary) sharing the claim's terms, each with its page when stated. The tool does NOT judge: compare the claim against the excerpts. If a number, date, article or cond
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 51 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Openinsurance Wiki compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 85% of 2,174 E-commerce servers
- Tools
- 10
- the typical E-commerce server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 2
- more than 80% of 1,047 E-commerce servers
- Downloads a week
- 15
- more than 3% of 411 E-commerce servers with a package
What its tools let an agent do: 10 read
Install Openinsurance Wiki in Claude Code, Cursor or VS Code
claude mcp add openinsurance-wiki -- uvx openinsurance-wiki-mcp
What the publisher says
From the Openinsurance Wiki repository's README, as published. We do not edit it. Read it on GitHub
openinsurance-wiki
A brain for a country's insurance market. A self-sufficient, open-source, country-agnostic framework that
turns a nation's public insurance documents into a rich, interconnected, source-cited knowledge base that any
AI agent can read.
Read it live: sluyasu.github.io/OpenInsurance - every page in this repo, browsable and searchable, no install.
Not a chatbot. Not a RAG black box. A transparent, reproducible knowledge graph: the repo contains the whole chain - it finds insurers' public general-conditions PDFs, downloads them, and turns each one into a faithful Markdown page that preserves the maximum of what the PDF actually says, with a citation back to the source - all cross-linked into a navigable graph of products, insurers, branches, regulations and concepts.
As far as we know, this is the only open-source, machine-readable, source-cited database of insurance products (the closest equivalents are commercial and closed). Point it at any country: the taxonomy is data, not code, and adding a country is a documented recipe (_meta/BOOTSTRAP-COUNTRY.md).
The dataset covers four countries - Belgium, France, Luxembourg and Switzerland - for a total of 39 insurers and 1,189 product pages (auto, home, health, liability, travel, legal protection, ...), each page cited to its source document:
The recipe was proven on Belgium first and has since been run three more times, which is what turned "country-agnostic" from a design claim into a tested one. Live counts are the generated coverage table in AGENTS.md, rebuilt from the data on every index run.
Use it in 2 minutes - no API key needed
The dataset ships in the repo, already built: 1,189 product pages across four countries, insurer pages, glossary, plus the structured JSON behind them. You only need an LLM key to re-extract from scratch, never to use it.
1. Read it. Online at sluyasu.github.io/OpenInsurance, or open the cloned repo as an Obsidian vault and the [[wikilinks]] become a navigable graph. (github.com itself does not render [[wikilinks]] as links - the site or the vault is the comfortable way.)
2. Plug it into an agent (MCP). The MCP server is keyless and read-only:
git clone https://github.com/sluyasu/OpenInsurance.git
cd OpenInsurance
python3 -m venv .venv && .venv/bin/pip install "mcp[cli]" pyyamlThen register it with any MCP client, e.g. Claude Code:
claude mcp add insurance-wiki -- "$(pwd)/.venv/bin/python" "$(pwd)/mcp/insurance_wiki_mcp.py"Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Openinsurance Wiki: common questions
- Is Openinsurance Wiki MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Openinsurance Wiki safety report
- How do I install Openinsurance Wiki?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Openinsurance Wiki need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Openinsurance Wiki maintained?
- The last commit was 90 days ago (2026-08-06). The latest release is v0.2.0.
- What can I use instead of Openinsurance Wiki?
- Servers from other publishers that do the same job: Savvly MCP server, GenesisPay MCP server and FlowScope UX Flow Analyser MCP server.
- How does Openinsurance Wiki compare with other E-commerce MCP servers?
- safety score 88/100 (higher than 85% of 2,174 E-commerce servers); tools 10 (the typical E-commerce server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Openinsurance Wiki
Same job from other publishers: the closest match first, then the best rated.
- SavvlySavvly MCP: query fund data, model projections, and compare against alternative retirement products.not reviewedGrowingA
GenesisPayLet an AI agent find and pay for x402 APIs and products in USDC on Base, within owner-set limits.not reviewedGrowingC- FlowScope UX Flow AnalyserTurn YouTube product demos into structured UX flow reports, and compare demos side by side.not reviewedGrowingB
- PostHog MCP ServerOfficial PostHog MCP Server for product analytics, feature flags, experiments, and more.not reviewedEstablishedA
- Loki ModeAutonomous spec-to-product coding-agent CLI with an MCP server exposing 39 tools over stdio.not reviewedEstablishedB