BackNine Life Insurance
REMOTE · APP.BACK9INS.COM
Compare life insurance quotes and start electronic applications with BackNine.
Available components
Last scanned (22 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
Recent critical change
Authorization (19 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_life_eapp_quote). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1891 tokens (~236/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://app.back9ins.com/api/v1/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.back9ins.com | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e251640a32d28e980e04584c8e3786dd |
| SANs: app.back9ins.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.back9ins.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| back9ins.com. | present | 2371 | 13 | Verified |
| app.back9ins.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; font-src 'self'; img-src 'self' portal-pictures.back9ins.com; object-src 'none'; frame-src 'none'; script-src 'self' ajax.cloudflare.com 'nonce-PP41uefvkeSriU8R9XbPPQ=='; style-src 'self' 'nonce-PP41uefvkeSriU8R9XbPPQ=='; base-uri 'self'; block-all-mixed-content |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.back9ins.com/api/v1/mcp/public | Verified | 200 | |
| http (plaintext) | http://app.back9ins.com/api/v1/mcp/public | HTTPS enforced | 301 | https://app.back9ins.com/api/v1/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_life_eapp ~158
Create an eApp from a quote_id returned by any public quote tool and return its private apply_link. Call only after the user selects that quote and explicitly asks to start an application. Retries for the same quote reuse the eApp. Give the user the private apply_link and explain that they must open it to continue in Quote & Apply, complete the remaining application steps, and sign where required. This MCP action does not complete or submit the application to a carrier or bind coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | Opaque quote_id from a public life quote tool; raw cache IDs and existing eApp IDs are not accepted |
| user_confirmed | boolean | yes | The user selected this quote and explicitly requested starting an application |
No output schema declared.
No examples provided.
get_life_quote_requirements ~65
Get required inputs for anonymous US life insurance and long-term-care quotes across enabled non-annuity product types, including product-specific inputs, solves, health labels, and rider filters. No name, email, phone, SSN, account, or existing application is needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_final_expense ~232
Get final-expense life insurance quotes, including small burial/funeral coverage. Supports the platform coverage range of $5,000 to $100,000,000, subject to carrier/product limits. No term duration. Uses monthly or annual payments and an explicit assumed health value. Each returned quote_id can be used with create_life_eapp after user selection.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdate | string | yes | Date of birth, YYYY-MM-DD |
| death_benefit | integer | yes | – |
| gender | string | yes | Carrier rating input, supplied by the user |
| guaranteed_issue | boolean | – | Optional guaranteed-issue-only filter; defaults to false |
| health | integer | yes | Explicit assumed final-expense health value. Use the health_classes in get_life_quote_requirements; never infer eligibility. |
| height | integer | – | Optional height in inches |
| mode | integer | yes | Payments per year: 1 annually or 12 monthly |
| smoker | string | yes | – |
| state | string | yes | – |
| usages | array | – | – |
| weight | integer | – | Optional weight in pounds |
No output schema declared.
No examples provided.
quote_life_eapp ~101
Get fresh non-annuity quotes for the eApp created through public MCP, using its saved rating inputs and optional scenario changes. Requires its private application_token. Does not change the application. Returned quote_id selections are bound to this application and its current revision.
| Name | Type | Req | Description |
|---|---|---|---|
| application_token | string | yes | Private application_token returned by create_life_eapp; an eApp ID, UUID, or completion URL is not accepted |
| changes | object | – | – |
No output schema declared.
No examples provided.
quote_life_insurance ~737
Quote all supported non-annuity products: term, non-med term, return-of-premium term, final expense (fex), UL, accumulation IUL (iul), protection IUL (piul), VUL where enabled/licensed, whole life, linked benefits, traditional LTC, and accidental death. Supports LTC/chronic illness riders on life products. Call get_life_quote_requirements first for enabled products and each product's schema/health labels. Use explicit user inputs. Returns consumer product details, comparison benefits, exam/application guidance, illustration values when available, and signed quote_id selections for create_life_eapp. Annuities are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| age_value | integer | – | Target age for cash-value solves |
| benefit_period | integer | – | Benefit years; -1 unlimited where supported |
| birthdate | string | yes | Date of birth, YYYY-MM-DD |
| cash_value | number | – | – |
| child_rider | boolean | – | – |
| child_rider_units | integer | – | – |
| crediting_rate_requested | number | – | Optional assumed illustration rate as a decimal; not a guaranteed return |
| death_benefit | integer | – | – |
| discount | string|null | – | – |
| elimination_period | integer | – | Waiting period in days |
| filter_chronic_illness_and_ltc | string | – | Explicit rider filter, including With LTC Rider; availability and definitions vary by product |
| gender | string | yes | Carrier rating input, supplied by the user |
| guaranteed_issue | boolean | – | Limit results to guaranteed-issue products |
| health | integer | – | User-supplied assumed health value. Get product-specific labels from get_life_quote_requirements. Never infer underwriting eligibility. |
| height | integer | – | Optional height in inches |
| home_health_care_waiver | boolean | – | – |
| income_end_age | integer | – | – |
| income_solve | string | – | – |
| income_start_age | integer | – | – |
| inflation_percentage | string|null | – | – |
| joint_party | object | – | – |
| joint_waiver_of_premium | boolean | – | – |
| lapse_protection_to_age | integer | – | – |
| living_benefits | boolean | – | – |
| loan_type | string | – | – |
| ltc_rider_percentage | number | – | Requested monthly acceleration percentage; carrier-specific limits apply |
| marital_status | string | – | – |
| mode | integer | yes | Payments per year: annual, semiannual, quarterly, monthly |
| monthly_benefit | number | – | Requested monthly care benefit in USD, for Base Premium solves |
| partner_discount | string|null | – | – |
| pay_duration | integer | – | Payment years; -1 lifetime, -65 until age 65, -100 until age 100, 1 single pay |
| pool_of_money | number | – | – |
| premium | number | – | Premium in USD at the requested payment frequency, for benefit/death-benefit solves |
| product_type | string | yes | – |
| return_of_premium_rider | string|null | – | – |
| save_age | boolean | – | Backdate to save age only when explicitly requested by the user |
| shared_care | boolean | – | – |
| smoker | string | yes | – |
| solve | string | – | – |
| state | string | yes | – |
| term_duration | integer | – | Requested level term in years; availability depends on carrier/product |
| usages | array | – | – |
| use_pool_of_money | boolean | – | – |
| waiver_of_premium | boolean | – | – |
| weight | integer | – | Optional weight in pounds |
No output schema declared.
No examples provided.
quote_term_life ~222
Get term-life quotes using explicit user-provided rating inputs. Results include consumer product details, benefit comparisons, and quote-based application guidance. Each result includes an opaque quote_id valid for 30 minutes. After the user selects a quote and requests an application, call create_life_eapp to get their application link. Never invent missing inputs or an underwriting class.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdate | string | yes | Date of birth, YYYY-MM-DD |
| death_benefit | integer | yes | – |
| gender | string | yes | Carrier rating input, supplied by the user |
| health | integer | yes | User-supplied assumed health value. Read product-specific labels from get_life_quote_requirements; never infer eligibility. |
| height | integer | – | Optional height in inches |
| mode | integer | yes | Payments per year: annual, semiannual, quarterly, monthly |
| smoker | string | yes | – |
| state | string | yes | – |
| term_duration | integer | yes | – |
| usages | array | – | – |
| weight | integer | – | Optional weight in pounds |
No output schema declared.
No examples provided.
update_life_eapp_insured ~200
Update the primary or joint insured's name, email, phone, or supported rating inputs for the eApp created through public MCP. Requires its private application_token and explicit user confirmation. Rating changes invalidate the selected quote and require fresh quotes before selection. SSNs, payment data, medical answers, agent/domain overrides, and signed/submitted application edits are not accepted. Give the user the private apply_link and explain that they must open it to continue in Quote & Apply, complete the remaining application steps, and sign where required. This MCP action does not complete or submit the application to a carrier or bind coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| application_token | string | yes | Private application_token returned by create_life_eapp; an eApp ID, UUID, or completion URL is not accepted |
| insured | object | yes | – |
| insured_role | string | – | Defaults to primary |
| user_confirmed | boolean | yes | The user explicitly requested these application changes |
No output schema declared.
No examples provided.
update_life_eapp_quote ~176
Select a quote returned by quote_life_eapp for that same application. Requires its private application_token, application-bound quote_id, and explicit user confirmation. Applies the selected rating inputs and quote, retains quote history, and returns the completion link. Rejects stale selections and locked/submitted applications. Give the user the private apply_link and explain that they must open it to continue in Quote & Apply, complete the remaining application steps, and sign where required. This MCP action does not complete or submit the application to a carrier or bind coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| application_token | string | yes | Private application_token returned by create_life_eapp; an eApp ID, UUID, or completion URL is not accepted |
| quote_id | string | yes | – |
| user_confirmed | boolean | yes | The user explicitly requested these application changes |
No output schema declared.
No examples provided.
How do I install the BackNine Life Insurance MCP server?
BackNine Life Insurance is a hosted endpoint at https://app.back9ins.com/api/v1/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.back9ins.com
claude mcp add --transport http com-back9ins-life-insurance 'https://app.back9ins.com/api/v1/mcp/public'
What is the BackNine Life Insurance MCP server?
BackNine Life Insurance is an MCP server listed in the public MCP registry as com.back9ins/life-insurance. Compare life insurance quotes and start electronic applications with BackNine. This page covers its hosted endpoint (https://app.back9ins.com/api/v1/mcp/public).
Is the BackNine Life Insurance MCP server safe to use?
BackNine Life Insurance scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BackNine Life Insurance MCP server expose?
BackNine Life Insurance exposes 8 tools: get_life_quote_requirements, quote_term_life, quote_final_expense, quote_life_insurance, create_life_eapp, and 3 more. Their descriptions and schemas cost roughly 1,891 tokens of context every time the server is loaded.
Does the BackNine Life Insurance MCP server require authentication?
No. We connected to BackNine Life Insurance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BackNine Life Insurance MCP server still maintained?
BackNine Life Insurance is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.