# com.savvly/savvly (remote · api.savvly.com)

Savvly MCP: query fund data, model projections, and compare against alternative retirement products.

- Trust score: 64/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.savvly.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-savvly-savvly/api.md), [page](https://verifymcp.io/servers/com-savvly-savvly/api)
- mcpb · `savvly-mcp-server.mcpb`: 13/100, [markdown](https://verifymcp.io/servers/com-savvly-savvly/https-github-com-savvly-savvly-mcp-releases-download-v1-0-86-savvly-mcp-server-m.md), [page](https://verifymcp.io/servers/com-savvly-savvly/https-github-com-savvly-savvly-mcp-releases-download-v1-0-86-savvly-mcp-server-m)
- npm · `@savvly/mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/com-savvly-savvly/savvly-mcp-server.md), [page](https://verifymcp.io/servers/com-savvly-savvly/savvly-mcp-server)
- nuget · `Savvly.McpServer`: 39/100, [markdown](https://verifymcp.io/servers/com-savvly-savvly/savvly-mcpserver.md), [page](https://verifymcp.io/servers/com-savvly-savvly/savvly-mcpserver)
- oci · `ghcr.io/savvly/savvly-mcp-server:1.0.86`: 9/100, [markdown](https://verifymcp.io/servers/com-savvly-savvly/ghcr-io-savvly-savvly-mcp-server-1-0-86.md), [page](https://verifymcp.io/servers/com-savvly-savvly/ghcr-io-savvly-savvly-mcp-server-1-0-86)
- pypi · `savvly-mcp-server`: 21/100, [markdown](https://verifymcp.io/servers/com-savvly-savvly/savvly-mcp-server-2.md), [page](https://verifymcp.io/servers/com-savvly-savvly/savvly-mcp-server-2)

## Channel facts

- Endpoint: `https://api.savvly.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.86`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 35/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3808 tokens (~238/item across 16 items; 8 tools + 8 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http com-savvly-savvly https://api.savvly.com/mcp
```

### Codex

```toml
[mcp_servers.com-savvly-savvly]
url = "https://api.savvly.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-savvly-savvly": {
      "type": "remote",
      "url": "https://api.savvly.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-savvly-savvly --url https://api.savvly.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-savvly-savvly:
    url: "https://api.savvly.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-savvly-savvly": {
      "type": "http",
      "url": "https://api.savvly.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

- [security] Tool “get_savvly_faq” rewrote its description, which is the text the model reads
- [security] Tool “get_savvly_product_info” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.85 → 1.0.86
- [functional] Server version: 1.0.82 → 1.0.85
- [cosmetic] “get_savvly_product_info” reworded the description of “section”

### 2026-07-28 (score 58, +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.

### 2026-07-27 (score 57, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (8)

### `get_savvly_product_info` (~173 tokens)

Get Savvly Product Info

Get complete product information about Savvly, an SEC-registered security offering longevity protection — use it whenever the user asks what Savvly is, how it works, its expenses, eligibility, or payouts, or wants an overview. Pass `section` to focus the answer (default 'all'). It renders an interactive product overview card the user expects to see. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

Input parameters:

- `section` (string): Which part of the product profile to focus the text on — one of 'all', 'overview', 'regulatory', 'investment', 'expenses', 'payouts', 'tax', 'distribution' (default 'all'). The full overview card alw…

Output parameters:

- `category` (string): Product category slug, e.g. 'longevity_benefit_fund'.
- `channels` (array): Distribution channels through which Savvly is offered.
- `company` (object): Issuer / advisor entity information.
- `description` (string): Long-form product description.
- `disclaimers` (object): SEC-style disclaimers and required legal language.
- `early_withdrawal` (object): Early-withdrawal / surrender terms and the value returned to the estate.
- `expenses` (object): Expense structure in basis points (common vs tracking shares) and the blended range; illustrations are net of expenses.
- `investment` (object): How contributions are invested: underlying assets (S&P 500 ETF), asset managers, minimum/maximum monthly and lump-sum amounts, market participation.
- `links` (object): Relevant URLs (website, disclosures, etc.).
- `longevity_pool` (object): How the longevity pool works — exited participants' unused shares may be allocated to remaining participants.
- `name` (string): Product name (e.g. 'Savvly Longevity Benefit').
- `next_steps` (object): Suggested next actions for an interested investor.
- `payout_schedule` (array): Milestone payout schedule at ages 80/85/90/95.
- `portability` (boolean): Whether the position is portable.
- `portability_note` (string): Detail on portability.
- `positioning_statement` (string): One-sentence positioning — what Savvly is and is NOT (not insurance, not an annuity).
- `regulatory` (object): Regulatory status: SEC registration, Investment Company Act of 1940, advisor, custodian, and is_insurance/is_annuity flags.
- `tagline` (string): Short marketing tagline.
- `tax_treatment` (object): Tax treatment of payouts and contributions.

### `compare_savvly_vs_alternative` (~193 tokens)

Compare Savvly vs Alternative Product

Get a structured comparison between Savvly and another retirement product type — use it whenever the user compares Savvly to annuities, target-date funds, managed-payout funds, or any alternative, or asks how Savvly stacks up. It renders an interactive comparison widget the user expects to see. Pass 'all' for the full matrix, or a specific product type. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

Input parameters:

- `alternative` (string): Which product type to compare Savvly against. Use EXACTLY one of: 'fixed_annuity', 'variable_annuity', 'indexed_annuity', 'target_date_fund', 'managed_payout_fund', or 'all' for the full matrix. Pick…

Output parameters:

- `comparison` (object): The selected alternative product's profile. Present when `alternative` is a specific product type (i.e. not 'all').
- `comparisons` (array): Full comparison matrix — one entry per alternative product type. Present when `alternative` is 'all'.
- `metadata` (object): Comparison dimensions, definitions, and source notes.
- `savvly` (object): Savvly's profile across the comparison dimensions.

### `project_savvly_lumpsum` (~893 tokens)

Project Savvly Lump-Sum Investment

Retirement projection for a lump-sum investment in the Savvly Longevity Benefit. Returns payout amounts at each milestone age (80, 85, 90, 95) with Savvly vs market alone cumulative totals, per-age breakdowns, and server-provided `_lower`/`_upper` range bounds. Use `_upper` as the central illustrative estimate and `_lower` to communicate downside. Suitable for retirement income planning, annuity alternative analysis, and longevity benefit illustration. Response embeds SEC-style disclaimers and per-field interpretation hints under `metadata`. Payout methodology — Savvly vs market alone: the payout values are calculated by comparing two investors of the same age committing the same principal. Investor 1 invests in the market with the Savvly Longevity Benefit; Investor 2 invests in the market alone (no longevity overlay). To make the comparison apples-to-apples, at each milestone age (80, 85, 90, 95) Investor 2 withdraws from their market alone portfolio the same dollar amount Investor 1 receives as a payout from Savvly. The `payout_market_alone_*` and `total_market_alone_*` figures are therefore what Investor 2 can actually withdraw to match Savvly's payouts before running out — they fall to 0 once the market alone portfolio is depleted. The `savvly_upside_*` (and `total_savvly_upside_*`) fields quantify how much more total money Investor 1 receives in payouts from Savvly than Investor 2 is able to withdraw over time to match those payouts. DISCLOSURE REQUIRED: display `disclosure.text` verbatim and link `disclosure.url` to the user alongside any figures from this response. Required by SEC Marketing Rule and FINRA Rule 2210 — do not paraphrase or omit. VISUALIZATION: this tool emits an interactive chart widget (MCP Apps — see `_meta.ui`) that the HOST renders inline and editable; other clients render only your text and show no chart. That widget is the canonical chart for these numbers: do NOT draw, generate, or re-render a duplicate of it. You MAY still create your…

Input parameters:

- `average_return` (integer): Expected average annual S&P 500 return % (default 8)
- `current_age` (integer): Investor's current age (default 40). Min 18 (the projection matrix floor); max 75 (max enrollment age)
- `funding_amount` (number): Lump sum investment in USD (default 10000)
- `withdrawal_age` (integer): Early-withdrawal age (default 82) — drives `early_withdrawal_value` and `total_payout_at_withdrawal_age_*` in the response

Output parameters:

- `disclosure` (object): DISCLOSURE REQUIRED: display `disclosure.text` and link `disclosure.url` to the user whenever you present any number from this response. Required by SEC Marketing Rule and FINRA Rule 2210. The richer…
- `inputs` (object): Echo of the validated input arguments passed to the tool.
- `metadata` (object)
- `result` (object): Raw projection envelope returned by the upstream estimator.
- `summary` (object): Convenience summary including a human-readable narrative.
- `visualization` (object): Recommended chart for this projection — a grouped bar chart of the milestone payouts in `result.payout_age_dependent_values` (Savvly vs market alone). Render it when the surface can display a graph.

### `project_savvly_monthly` (~1032 tokens)

Project Savvly Monthly Contributions

Retirement projection for monthly contributions to the Savvly Longevity Benefit over a number of years. Returns payout amounts at milestone ages 80/85/90/95 with Savvly vs market alone cumulative totals, per-age breakdowns, and server-provided `_lower`/`_upper` range bounds. Use `_upper` as the central illustrative estimate and `_lower` to communicate downside. Suitable for retirement savings planning, annuity alternative comparison, and longevity benefit illustration. Supports an optional annual contribution increase and an optional early-withdrawal age. Contributions must finish by age 80: an omitted `contribution_years` auto-fits this, and an explicit one must satisfy `current_age + contribution_years` ≤ 80. Disclaimers + per-field hints under `metadata`. Payout methodology — Savvly vs market alone: the payout values are calculated by comparing two investors of the same age committing the same principal. Investor 1 invests in the market with the Savvly Longevity Benefit; Investor 2 invests in the market alone (no longevity overlay). To make the comparison apples-to-apples, at each milestone age (80, 85, 90, 95) Investor 2 withdraws from their market alone portfolio the same dollar amount Investor 1 receives as a payout from Savvly. The `payout_market_alone_*` and `total_market_alone_*` figures are therefore what Investor 2 can actually withdraw to match Savvly's payouts before running out — they fall to 0 once the market alone portfolio is depleted. The `savvly_upside_*` (and `total_savvly_upside_*`) fields quantify how much more total money Investor 1 receives in payouts from Savvly than Investor 2 is able to withdraw over time to match those payouts. DISCLOSURE REQUIRED: display `disclosure.text` verbatim and link `disclosure.url` to the user alongside any figures from this response. Required by SEC Marketing Rule and FINRA Rule 2210 — do not paraphrase or omit. VISUALIZATION: this tool emits an interactive chart widget (MCP Apps — see `_meta.ui`) that the HOS…

Input parameters:

- `average_return` (integer): Expected average annual S&P 500 return % (default 8)
- `contribution_years` (integer): Number of years contributing. Omit to use a sensible default of min(27, 80 − current_age) — 27 for the canonical age-40 scenario, and always small enough that contributions finish by age 80 (the advi…
- `current_age` (integer): Investor's current age (default 40). Min 18 (the projection matrix floor); max 75 (max enrollment age)
- `installment_increase_percentage` (number): Optional annual % increase applied to monthly contributions
- `monthly_amount` (number): Monthly deposit in USD (default 100)
- `withdrawal_age` (integer): Early-withdrawal age (default 82) — drives `early_withdrawal_value` and `total_payout_at_withdrawal_age_*` in the response

Output parameters:

- `disclosure` (object): DISCLOSURE REQUIRED: display `disclosure.text` and link `disclosure.url` to the user whenever you present any number from this response. Required by SEC Marketing Rule and FINRA Rule 2210. The richer…
- `inputs` (object): Echo of the validated input arguments passed to the tool.
- `metadata` (object)
- `result` (object): Raw projection envelope returned by the upstream estimator.
- `summary` (object): Convenience summary including a human-readable narrative.
- `visualization` (object): Recommended chart for this projection — a grouped bar chart of the milestone payouts in `result.payout_age_dependent_values` (Savvly vs market alone). Render it when the surface can display a graph.

### `project_retirement_with_savvly` (~765 tokens)

Project Retirement Trajectory With Savvly

Full retirement simulation showing the projected savings trajectory WITH and WITHOUT a Savvly allocation across the planning horizon (current_age → life_expectancy). Requires current_age ≤ retirement_age ≤ life_expectancy. Returns `gap_score`, `possible_higher_monthly_paycheck`, a server-provided headline message, and a per-year `age_dependent_values[]` timeline. Disclaimers + per-field hints under `metadata`. DISCLOSURE REQUIRED: display `disclosure.text` verbatim and link `disclosure.url` to the user alongside any figures from this response. Required by SEC Marketing Rule and FINRA Rule 2210 — do not paraphrase or omit. VISUALIZATION: this tool emits an interactive chart widget (MCP Apps — see `_meta.ui`) that the HOST renders inline and editable; other clients render only your text and show no chart. That widget is the canonical chart for these numbers: do NOT draw, generate, or re-render a duplicate of it. You MAY still create your OWN, DIFFERENT visualization (e.g. a table or an alternate breakdown) and place it wherever you judge best — only the MCP App widget's position is constrained. Do NOT claim or imply a chart is visible (avoid 'the chart above shows…'); you cannot tell whether the host rendered the widget. Summarize the key figures in prose and show the `disclosure` text and link, and reference the widget only conditionally (e.g. 'if your client shows the interactive chart, its fields are editable to re-run the projection'). ORDER: BEFORE you call this tool, ALWAYS write at least one short lead-in paragraph (1-3 sentences) framing what the projection will show — do NOT invent specific figures you do not have yet. On hosts that render the widget inline at the tool call, this keeps your text ahead of the chart so the widget is never the first thing shown; THEN call the tool (this lead-in is framing, NOT asking the user for inputs — still call it in the same turn without waiting) and give the grounded figures + disclosure after it returns. This lead-in ru…

Input parameters:

- `annual_income_increase` (number): Annual contribution % increase (default 2)
- `current_age` (integer): Current age (default 40)
- `current_retirement_savings` (number): Current total retirement savings in USD (default 60000)
- `inflation_rate` (number): Expected annual inflation rate % (default 3)
- `life_expectancy` (integer): Planning horizon (default 100)
- `monthly_contribution` (number): Monthly retirement contribution in USD (default 1000)
- `monthly_paycheck` (number): Desired monthly retirement paycheck in USD (default 4500)
- `other_retirement_income` (number): Other monthly retirement income in USD (default 1600)
- `percentage_in_savvly` (number): Percentage of the retirement portfolio allocated to Savvly (default 5)
- `post_retirement_return` (number): Expected post-retirement annual return % (default 5)
- `pre_retirement_return` (number): Expected pre-retirement annual return % (default 6)
- `retirement_age` (integer): Planned retirement age (default 68)

Output parameters:

- `disclosure` (object): DISCLOSURE REQUIRED: display `disclosure.text` and link `disclosure.url` to the user whenever you present any number from this response. Required by SEC Marketing Rule and FINRA Rule 2210.
- `inputs` (object)
- `metadata` (object)
- `result` (object)
- `summary` (object): Convenience summary. The narrative carries the canonical full-disclosures URL inline; display it verbatim alongside any figures from this response.
- `visualization` (object): Recommended chart for this projection — a year-by-year area chart of `result.age_dependent_values` (savings with vs. without Savvly). Render it when the surface can display a graph. The richer `metad…

### `check_savvly_eligibility` (~162 tokens)

Check Savvly Eligibility

Check if a person is eligible to invest in the Savvly Longevity Benefit. Eligibility is based on age (no minimum; maximum enrollment age 75), US residency, and distribution channel (individual, employer-sponsored, advisor-placed). Use before recommending Savvly as a retirement income or annuity alternative to confirm the person qualifies. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

Input parameters:

- `age` (integer, required): Person's current age
- `channel` (string): Distribution channel — one of 'individual', 'employer', 'advisor' (default 'individual').
- `us_resident` (boolean): Whether the person is a US resident

Output parameters:

- `age_eligible` (boolean): True if age is at or under the maximum enrollment age (75); the filing sets no minimum age.
- `channel` (string): Distribution channel under consideration for this check.
- `criteria` (object): Full eligibility-criteria reference object (age range, residency, accredited-investor flag, channel requirements).
- `eligible` (boolean): True if every eligibility criterion (age + residency) is satisfied.
- `message` (string): Human-readable explanation of the eligibility outcome.
- `residency_eligible` (boolean): True if the US-residency requirement is satisfied.

### `get_savvly_faq` (~153 tokens)

Get Savvly FAQ

Get answers to frequently asked questions about Savvly. Use when the user has specific questions about how Savvly works, expenses, withdrawals, or regulatory status. It is a convenience view of `search_savvly_content` scoped to the factual FAQ; for richer, audience-specific Q&As (employee / advisor / broker / employer), use `search_savvly_content` instead. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

Input parameters:

- `section` (string): Filter the FAQ to one section (kebab-case, e.g. 'tax-legacy'); 'all' returns every entry.

Output parameters:

- `entries` (array): Filtered FAQ entries (the audience:'general' Q&A slice).
- `section` (string): Section filter applied to produce this result set ('all' if no filter).
- `total` (integer): Count of FAQ entries returned.

### `search_savvly_content` (~303 tokens)

Search Savvly Q&A Content Library

Search the Savvly Q&A Content Library — audience-tagged questions and answers compiled from Savvly's marketing collateral plus the factual FAQ, organized by stakeholder (employee, advisor, broker, employer, universal, general) and section (kebab-case slugs, e.g. 'tax-legacy', 'retention-talent-strategy', 'implementation'). Use this when the user asks about Savvly's positioning, value props, audience-specific talking points, or Q&A-style messaging. Each entry carries the verbatim answer plus any disclaimer footnotes attached to it in the source. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

Input parameters:

- `audience` (string): Restrict to one stakeholder audience. Use EXACTLY one of: 'employee', 'advisor', 'broker', 'employer', 'universal', or 'general' ('general' is the factual FAQ). Omit to search across all audiences.
- `limit` (integer): Cap on matched entries returned. Default 20, max 50.
- `query` (string): Free-text search over questions, answers, and footnotes (case-insensitive). Multi-word queries match entries containing ANY of the words, ranked by relevance.
- `section` (string): Substring match against section slugs (e.g. 'tax', 'retention', 'eligibility'). Case-insensitive.

Output parameters:

- `available_sections` (array): Section slugs available within the (optionally) selected audience.
- `entries` (array): Matched Q&A entries.
- `filter_applied` (object): Echo of the filters that produced this result set.
- `matched` (integer): Count of entries matching the supplied filters.
- `total_in_library` (integer): Total Q&A entry count in the library across all audiences.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-savvly-savvly/api#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 60
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 57

## Links

- Remote endpoint: https://api.savvly.com/mcp
- Repository: https://github.com/Savvly/savvly-mcp
- Website: https://savvly.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-savvly-savvly/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-savvly-savvly/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-savvly-savvly/api