ApolloTech Insurance MCP
Server Details
ApolloTech Insurance MCP connects any MCP-compatible assistant or agent to real-time, multi-carrier quotes, carrier eligibility questionnaires and consent-backed application submission.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool targets a distinct step in a linear pipeline: resolve_zip_counties (location), quote_carriers (pricing), get_eligibility_questionnaires (knockout screening), and submit_enrollment (write). Their purposes do not overlap, so an agent can select unambiguously. The heavy cross-referencing in descriptions reinforces ordering rather than creating confusion.
All four names use the same snake_case verb_noun convention: resolve_zip_counties, quote_carriers, get_eligibility_questionnaires, submit_enrollment. The verb styles (resolve/quote/get/submit) match each tool's action clearly. No style mixing or vague names.
Four tools is on the lean side but each maps to an essential stage of the quote-to-enroll workflow. Nothing appears redundant, though the surface is minimal enough that it could feel thin if more read-only operations were expected. Reasonable for a narrow, high-stakes domain.
The core lifecycle is covered: resolve location, quote, screen eligibility, and file enrollment, including retry/idempotency guidance for submission. Minor gaps remain, such as no standalone plan-detail retrieval beyond compact summaries or an explicit submission-status check, but agents can work around these via the returned fields.
Publisher details
- Operator
- ApolloTech
- Operator website
- https://ApolloTe.ch · Publisher source
- Vendor relationship
- Not available
- Documentation
- https://mcp.apollote.ch/docs.html · Publisher source
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- Access is granted per partner. We review every request and reply with next steps, including a test key for our QA environment. · Publisher source
Available Tools
4 toolsget_eligibility_questionnairesAInspect
Fetches each carrier's eligibility questionnaire for the plans the applicant selected. Pass selectedPlans as {carrier, planId} from quote_carriers, with the SAME applicants (primary, spouse, dependents), location, household and effectiveDate used for the quote. UHC and ONESHARE have no questionnaires and are simply absent from the result (not an error); carriers with no questions are also absent. An empty categories list with a message means nothing to ask or a rejected selection. A question with expectedAnswer is a knockout: any other answer means the carrier will decline, so do not enroll in that carrier's plans. Failed carriers appear in errors[] (TIMEOUT/CIRCUIT_OPEN/UNAVAILABLE retryable; CARRIER_ERROR not). Show the user questionTextPlain when present (questionText may contain HTML), but send questionText and answerText back VERBATIM in submit_enrollment's answers, with questionsId. PLAN_NOT_FOUND means the plan is no longer offered for these details: quote again.
Inputs: primary (required), location (required), selectedPlans (required), spouse, +5 more.
quote_carriersAInspect
Fans out concurrently to granted carriers for quotes. Requires location (fipsCode, zipCode, state, county = countyName) from resolve_zip_counties and primary applicant (gender, dateOfBirth). Returns carriers[] with compact plan summaries (planId, planName, premium, fees, deductible, key benefits); per-carrier failures are in errors[] (TIMEOUT/CIRCUIT_OPEN/UNAVAILABLE are retryable; CARRIER_ERROR is not). Partial results are normal — do not treat a non-empty errors[] as failure. questionsRequired=true means get_eligibility_questionnaires must be called before enrolling in that carrier's plans. carriers/categories narrow the request; naming one you are not granted fails the whole request (403) — then retry without that filter. Use maxPlansPerCarrier to see only the cheapest few per carrier. To use a plan later, pass {carrier, planId} in selectedPlans, together with the SAME applicants, location, household and effectiveDate used here.
Inputs: primary (required), location (required), spouse, carriers, +8 more.
resolve_zip_countiesAInspect
Resolves a 5-digit ZIP to one or more {fipsCode, zipCode, countyName, state} rows (returned as counties, with hasMultipleCounties). Call this FIRST before quoting. Most ZIPs return one county; a ZIP straddling a county line returns several and the applicant must choose, because premiums differ by county. Pass the chosen row on every later request as location {fipsCode, zipCode, state, county: countyName}.
Inputs: zipCode (required).
submit_enrollmentAInspect
HIGH-STAKES WRITE: Files applicants, contact, selected plans and questionnaire answers for MANUAL completion by an Apollo agent — this is not an enrollment confirmation. Pass selectedPlans as {carrier, planId} from quote_carriers, with the SAME applicants, location, household and effectiveDate used for the quote. Never enroll in a carrier's plans after a knockout answer (an answer other than expectedAnswer). Requires explicitUserConsent=true and consentStatement: the user's own message giving consent, quoted VERBATIM (never paraphrased or written by you). Only call after the user has explicitly agreed to submit. Success only when filed=true (status SYNCED/SKIPPED, or BACKUP_FILED: the API couldn't hand it off, so it went straight to an Apollo agent; don't resubmit). If filed=false (RECEIVED/SYNC_FAILED/upstream unavailable), call again with IDENTICAL arguments — the server derives the idempotency key from them, so an identical retry resumes the same submission and never files twice. PLAN_NOT_FOUND means a plan is no longer offered: quote again. Give the user the submissionId as their reference and relay nextStep verbatim; do not promise anything else.
Inputs: location (required), applicants (required), contactInfo (required), effectiveDate (required), +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Real, bindable home & auto insurance quotes via MCP — actual carrier rates, not estimates. Texas today, expanding across the US. AI agents can check eligibility, run a live multi-carrier quote, compare options (carrier names hidden until bind), and hand the customer a secure link where a licensed agent finalizes coverage — never an automated purchase. No sign-up or API key required; optional free partner keys for integrators.
Real, bindable home & auto insurance quotes via MCP (Texas, expanding); human-completed bind.
Agent-native insurance quoting protocol — sandbox, MCP + REST, eligibility pre-flight
保险产品搜索、推荐、保费试算、核保预检。覆盖65家保司483款产品。China insurance MCP server.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search, compare, recommend, quote, and pre-underwrite Chinese insurance products via MCP, covering 158 insurers and 489 products.2-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to interact with GEICO insurance services, including getting quotes, managing policies, filing claims, making payments, retrieving ID cards, requesting roadside assistance, and reporting accidents.13 npm1MIT
- AlicenseAqualityDmaintenanceMCP server that exposes life-insurance back-office tools (policy document search, application status, product/underwriting rules) to LLM agents. Enables agents to retrieve policy documents, check application status, and evaluate underwriting rules via hybrid search and rule lookup.3MIT
- FlicenseAqualityDmaintenanceEnables interaction with IntelliMatch recruiting and iSuite insurance systems through spec-driven MCP tools, allowing natural language queries for candidate search, policy management, claims, and workflows.28-
Glama MCP Gateway
Add one secure layer between your agents and this server.