Model Context Protocol (MCP) server for freee API integration
Eventual Premium Lock 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.
What it does
Quote and buy Eventual's Premium Lock for home and auto insurance premiums.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http eventual-premium-lock-mcp https://prod.api.eventualclimate.com/mcp/premium-lock
# 2 — ask your agent for something these tools do
# get_product_catalog, read_declarations_page, create_quote and 4 more
Eventual Premium Lock costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 eventual-premium-lock-mcp https://prod.api.eventualclimate.com/mcp/premium-lockReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
7 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.
What Premium Lock is, per product line and for the bundle: marketing's approved description, example fees and disclosures. Gathering order: first ask for the consumer's email. Then look for their home or auto insurance declarations page in their email and files; if you find one, send it to read_declarations_page and pass the fields it returns to create_quote. Otherwise ask the consumer for the fi
No parameter schema on file.
Read a home or auto insurance declarations page (PDF, PNG or JPEG, up to 10 MB). Returns the detected product line, the create_quote fields it found, and missing_required: the fields to ask the consumer for before calling create_quote. Gathering order: first ask for the consumer's email. Then look for their home or auto insurance declarations page in their email and files; if you find one, send i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The consumer's email. | |
| document_base64 | string | yes | The file's bytes, base64 encoded. |
| filename | string | no | — |
Start pricing a Premium Lock quote for the consumer, whose email goes in insured.email. Returns a quote_id; poll get_quote until its status is complete. Gathering order: first ask for the consumer's email. Then look for their home or auto insurance declarations page in their email and files; if you find one, send it to read_declarations_page and pass the fields it returns to create_quote. Otherwi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| insured | no | — | |
| policy | no | — | |
| partner_ref | no | The partner's own policy/quote identifier, echoed back on every response and webhook. | |
| product_line | string | no | — |
| auto | no | — | |
| referral_token | no | A referral partner's signed token, when one sent the consumer. Recorded as that referrer's claim on the quote; a token that does not verify is ignored and the quote is made anyway. | |
| idempotency_key | string | no | Optional. Defaults to a hash of the body, so a repeated call returns the first quote instead of creating another. |
The quote's status and, once complete, its pricing, checkout_url, purchase_options and required_disclosures. Gathering order: first ask for the consumer's email. Then look for their home or auto insurance declarations page in their email and files; if you find one, send it to read_declarations_page and pass the fields it returns to create_quote. Otherwise ask the consumer for the fields create_qu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | The quote_id create_quote returned. |
Email the consumer on the quote a link to buy it on Eventual's site. Use it when the consumer would rather finish later or when another tool answers daily_cap. Gathering order: first ask for the consumer's email. Then look for their home or auto insurance declarations page in their email and files; if you find one, send it to read_declarations_page and pass the fields it returns to create_quote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | The quote to send. |
Buy a complete quote. First show the consumer every disclosure in the quote's required_disclosures word for word and the Terms of Service, and ask the no_claims question; pass what they affirmed as consent, echoing the quote's disclosure_set_id and disclosure_text_sha256, and the billing_interval they chose. When the quote's purchase_options include mcp_app and this app can show embedded checkouts
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | The quote to buy. |
| consent | no | Required to start. When finishing, optional, and it must be the consent given at the start. | |
| billing_interval | no | When starting, the interval the consumer chose from the quote's pricing. Omitted, the quote's own. |
Finish an in-conversation purchase with the payment_session_id the checkout returned. The checkout calls this itself; call it only to check on a purchase it reported pending. Answers active once bought or pending while the payment clears. Gathering order: first ask for the consumer's email. Then look for their home or auto insurance declarations page in their email and files; if you find one, sen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | The quote to buy. |
| payment_session_id | yes | The session_id the embedded checkout posted back. | |
| consent | no | Required to start. When finishing, optional, and it must be the consent given at the start. |
- 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 Eventual Premium Lock or to call it, at any volume.
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.
| 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 |
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.
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_product_catalog | no tags | |
| read_declarations_page | no tags | |
| create_quote | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_quote | no tags | |
| send_checkout_email | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| purchase_quote | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| complete_purchase | 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
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.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Eventual Premium Lock can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.