DEMO — all data is fictional
One MCP server for a vision-benefits member: plan maths, network, appointments, claims and frame shopping. Built to show what a member-facing agent could do. No real member, provider or claim data is present, and nothing here represents any real insurer.
claude mcp add --transport http argus https://argus-mcp.equationx.ai/mcp --header "Authorization: Bearer <key>"
claude.ai custom connector: https://argus-mcp.equationx.ai/mcp?key=<key>.
Add ?toolsets=all to preload every group.
Seven always on; the rest load when a question needs them, so a simple pricing question doesn't pay for the claims and booking schemas.
Always on: get_member_profile, get_benefits,
estimate_cost, find_providers, save_note,
find_capability, run_capability.
| Group | Tools |
|---|---|
network | check_retailer_network, get_provider_details, compare_retailer_options |
appointments | find_appointment_slots, book_appointment, cancel_appointment |
claims | list_claims, explain_claim |
commerce | search_frames, apply_benefits_to_cart |
eligibility | check_eligibility, household_benefit_summary |
reference | describe_plan_terms, describe_data_model |
Every tool call runs inside a Postgres transaction restricted by row-level security to the members that API key may see. The agent cannot read another household's record even if instructed to — the database refuses. That is enforcement, not prompt discipline.