Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
BackNine Life Insurance is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Compare life insurance quotes and start electronic applications with BackNine.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http backnine-life-insurance-mcp https://app.back9ins.com/api/v1/mcp/public
# 2 — ask your agent for something these tools do
# get_life_quote_requirements, quote_term_life, quote_final_expense and 5 more
BackNine Life Insurance costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BAAll 2 servers
back9ins2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http backnine-life-insurance-mcp https://app.back9ins.com/api/v1/mcp/publicReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | — |
| birthdate | string | yes | Date of birth, YYYY-MM-DD |
| 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. |
| smoker | string | yes | — |
| usages | array | no | — |
| death_benefit | integer | yes | — |
| term_duration | integer | yes | — |
| mode | integer | yes | Payments per year: annual, semiannual, quarterly, monthly |
| height | integer | no | Optional height in inches |
| weight | integer | no | Optional weight in pounds |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | — |
| birthdate | string | yes | Date of birth, YYYY-MM-DD |
| gender | string | yes | Carrier rating input, supplied by the user |
| health | integer | yes | Explicit assumed final-expense health value. Use the health_classes in get_life_quote_requirements; never infer eligibility. |
| smoker | string | yes | — |
| usages | array | no | — |
| death_benefit | integer | yes | — |
| mode | integer | yes | Payments per year: 1 annually or 12 monthly |
| height | integer | no | Optional height in inches |
| weight | integer | no | Optional weight in pounds |
| guaranteed_issue | boolean | no | Optional guaranteed-issue-only filter; defaults to false |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | — |
| birthdate | string | yes | Date of birth, YYYY-MM-DD |
| gender | string | yes | Carrier rating input, supplied by the user |
| health | integer | no | User-supplied assumed health value. Get product-specific labels from get_life_quote_requirements. Never infer underwriting eligibility. |
| smoker | string | yes | — |
| usages | array | no | — |
| death_benefit | integer | no | — |
| mode | integer | yes | Payments per year: annual, semiannual, quarterly, monthly |
| height | integer | no | Optional height in inches |
| weight | integer | no | Optional weight in pounds |
| product_type | string | yes | — |
| solve | string | no | — |
| premium | number | no | Premium in USD at the requested payment frequency, for benefit/death-benefit solves |
| pay_duration | integer | no | Payment years; -1 lifetime, -65 until age 65, -100 until age 100, 1 single pay |
| living_benefits | boolean | no | — |
| waiver_of_premium | boolean | no | — |
| child_rider | boolean | no | — |
| child_rider_units | integer | no | — |
| save_age | boolean | no | Backdate to save age only when explicitly requested by the user |
| term_duration | integer | no | Requested level term in years; availability depends on carrier/product |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_token | string | yes | Private application_token returned by create_life_eapp; an eApp ID, UUID, or completion URL is not accepted |
| user_confirmed | boolean | yes | The user explicitly requested these application changes |
| quote_id | string | yes | — |
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 accepte
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_token | string | yes | Private application_token returned by create_life_eapp; an eApp ID, UUID, or completion URL is not accepted |
| user_confirmed | boolean | yes | The user explicitly requested these application changes |
| insured_role | string | no | Defaults to primary |
| insured | object | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BackNine Life Insurance or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest1e0f5bcd40ece9b18eeb77a84759ec9d3156675c38d41ed33b6180666fca7c53
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_life_quote_requirements | no tags | |
| quote_term_life | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| quote_final_expense | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| quote_life_insurance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_life_eapp | state-write | state-write: declares readOnlyHint: false |
| quote_life_eapp | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| update_life_eapp_quote | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_life_eapp_insured | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1e0f5bcd40ece9b1
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BackNine Life Insurance can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.