insurance-claim-mcp
Related Servers
Alternatives to insurance-claim-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables insurance claims review assistance by querying a knowledge graph of Korean standard insurance terms, restoring applicable policy versions by enrollment date, and returning coverage/exclusion determinations with cited provisions.MIT
- AlicenseNot gradedqualityBmaintenanceEvaluates proposed x402 payments against a local policy and returns pay, review, or do_not_pay, while also listing and evaluating outstanding authorizations to flag double-pay or limbo risk.4MIT

costkits-mcpofficial
AlicenseAqualityCmaintenanceProvides live US healthcare cost data including procedure cost estimates, provider pricing, insurance coverage rules, and medical bill analysis using real hospital transparency and CMS data.1256 npmMIT- AlicenseAqualityBmaintenanceUS federal student loan repayment math for AI agents, from a parity-verified engine rather than estimated. RAP, IBR, ICR, PAYE and tiered Standard payments with forgiveness timing and tax on forgiveness, plus the plans a borrower is excluded from and the rule why, such as Parent PLUS not qualifying for RAP. No key to start; keyed answers at mcp.finology.tech/mcp add citations.377 npmMIT
- FlicenseNot gradedqualityAmaintenanceRead-only, key-less MCP for Japanese home-visit-nursing reimbursement rules: every requirement carries its source and that source's standing (statute / agency / secondary), and anything unconfirmed is published as unconfirmed. It returns evidence, never a billing decision.1-
- AlicenseNot gradedqualityCmaintenanceEnables assistants to compute 2026 health-insurance subsidy amounts, federal poverty level thresholds, 400% FPL cliff effects, and excess advance credit repayment caps using primary-source rules. It returns structured JSON plus plain-English summaries with sourcing and as-of dates.MIT
TDQS
Scored across 11 tools
Most tools map to a distinct resource+action (onboarding, user, policy, rider, rules, claim evaluation). The main overlap is register_user_policy, which explicitly says it registers *or updates* a policy, blurring its boundary with update_user_rider and resolve_user_rider. The three guide/list tools (get_onboarding_guide, get_document_request_guide, list_standard_rules) are related but distinguishable by descriptions.
Every tool follows a clean snake_case verb_noun pattern: get_*, list_*, register_*, resolve_*, update_*, delete_*, evaluate_*. Verbs are used consistently for their action type with no camelCase or stylistic mixing.
11 tools sit squarely in the well-scoped range and each covers a meaningful piece of the claim workflow (onboarding, user, policies, riders, rules, evaluation). No obviously redundant or filler tools.
The surface covers onboarding, user registration/profile, policy CRUD, rider resolution/updating, standard rules, and stateless claim evaluation, so core lifecycle is present. Minor gaps exist: no delete-user or profile-update operation, no standalone rider deletion, and no persisted claim history, but these are workable around.