Claims Index MCP server
DamageRestore HQ: the median paid water damage claim, read from NFIP claim records (2023 to...
C68/100grade C
Adoption
New
60 downloads/wk
Reviews
Write oneNobody has reviewed Claims Index yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Claims Index tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- Code scan3 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
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityverified namespace with website, no repo4/10
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @ellul-estate/damagerestorehq-com-claims-index-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add claims-index -- npx -y @ellul-estate/damagerestorehq-com-claims-index-mcp
Claims Index: common questions
- Is Claims Index MCP server safe?
- With care: it is graded C, so read the findings first (68/100). Read the Claims Index safety report
- How do I install Claims Index?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Claims Index need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Claims Index maintained?
- The latest release is v1.0.0.