com.savvly/savvly

Est-ce que com.savvly/savvly est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.savvly/savvly » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• check_savvly_eligibility≈ 592 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • age · integer · requis
    Person's current age
  • channel · string · optionnel · individual | employer | advisor
    Distribution channel — one of 'individual', 'employer', 'advisor' (default 'individual').
  • us_resident · boolean · optionnel
    Whether the person is a US resident

  Exemple d'appel

  {"name": "check_savvly_eligibility", "arguments": {"age": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"channel": "individual", "message": "texte", "criteria": {}, "eligible": true, "age_eligible": true, "residency_eligible": true}}

• compare_savvly_vs_alternative≈ 3937 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • alternative · string · optionnel · fixed_annuity | variable_annuity | indexed_annuity | target_date_fund | managed_payout_fund | all
    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 a SPECIFIC annuity subtype — there is no generic 'annuity'.

  Exemple d'appel

  {"name": "compare_savvly_vs_alternative", "arguments": {"alternative": "fixed_annuity"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"savvly": {}, "metadata": {}, "comparison": {}, "comparisons": []}}

• get_savvly_faq≈ 547 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • section · string · optionnel · all | understanding-savvly | investment-custody | payouts | withdrawals-estate | expenses-cost | tax-legacy | employer-portability
    Filter the FAQ to one section (kebab-case, e.g. 'tax-legacy'); 'all' returns every entry.

  Exemple d'appel

  {"name": "get_savvly_faq", "arguments": {"section": "all"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "entries": [], "section": "texte"}}

• get_savvly_product_info≈ 1480 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • section · string · optionnel · all | overview | regulatory | investment | expenses | payouts | tax | distribution
    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 always renders regardless.

  Exemple d'appel

  {"name": "get_savvly_product_info", "arguments": {"section": "all"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "links": {}, "company": {}, "tagline": "texte", "category": "texte", "channels": [], "expenses": {}, "investment": {}, "next_steps": {}, "regulatory": {}, "description": "texte", "disclaimers": {}}}

• project_retirement_with_savvly≈ 3833 tokens

  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 rule applies to the MCP App widget only; any visualization you create yourself may appear wherever you judge best. INPUTS: every parameter is OPTIONAL and defaults to a sensible value. Call this tool IMMEDIATELY — pass only the values the user explicitly stated and omit the rest. Do NOT ask the user for starting values, assumptions, or missing parameters before calling; the rendered widget has editable fields so they adjust age, amounts, and other assumptions inline after it appears.

  Paramètres, retour & exemple (12)

  Paramètres

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

  Exemple d'appel

  {"name": "project_retirement_with_savvly", "arguments": {"current_age": 1, "inflation_rate": 1, "retirement_age": 1, "life_expectancy": 1, "monthly_paycheck": 1, "monthly_contribution": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"inputs": {}, "result": {}, "summary": {}, "metadata": {}, "disclosure": {}, "visualization": {}}}

• project_savvly_lumpsum≈ 4828 tokens

  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, a `_central` estimate and the `_lower`/`_upper` range around it. Use `_central` as the single estimate and `_lower`/`_upper` to show the range. 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 as the central estimate of Investor 1's Savvly payout. The `payout_market_alone_*` and `total_market_alone_*` figures are therefore what Investor 2 can actually withdraw to match Savvly's central payouts before running out — they fall to 0 once the market alone portfolio is depleted. It is one series, so their `_lower` and `_upper` fields are equal. 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: `_central` is the single estimate, and `_lower` can be negative at the early milestones, where market alone still matches the central payout. 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 rule applies to the MCP App widget only; any visualization you create yourself may appear wherever you judge best. INPUTS: every parameter is OPTIONAL and defaults to a sensible value. Call this tool IMMEDIATELY — pass only the values the user explicitly stated and omit the rest. Do NOT ask the user for starting values, assumptions, or missing parameters before calling; the rendered widget has editable fields so they adjust age, amounts, and other assumptions inline after it appears.

  Paramètres, retour & exemple (4)

  Paramètres

  • current_age · integer · optionnel
    Investor's current age (default 40). Min 18 (the projection matrix floor); max 75 (max enrollment age)
  • average_return · integer · optionnel
    Expected average annual S&P 500 return % (default 8)
  • funding_amount · number · optionnel
    Lump sum investment in USD (default 10000). Min 100 (the product minimum); max 1,000,000 (the projection model's input limit, not an investment limit)
  • withdrawal_age · integer · optionnel
    Early-withdrawal age (default 82) — drives `early_withdrawal_value` and `total_payout_at_withdrawal_age_*` in the response

  Exemple d'appel

  {"name": "project_savvly_lumpsum", "arguments": {"current_age": 1, "average_return": 1, "funding_amount": 1, "withdrawal_age": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"inputs": {}, "result": {}, "summary": {}, "metadata": {}, "disclosure": {}, "visualization": {}}}

• project_savvly_monthly≈ 5021 tokens

  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, a `_central` estimate and the `_lower`/`_upper` range around it. Use `_central` as the single estimate and `_lower`/`_upper` to show the range. 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 as the central estimate of Investor 1's Savvly payout. The `payout_market_alone_*` and `total_market_alone_*` figures are therefore what Investor 2 can actually withdraw to match Savvly's central payouts before running out — they fall to 0 once the market alone portfolio is depleted. It is one series, so their `_lower` and `_upper` fields are equal. 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: `_central` is the single estimate, and `_lower` can be negative at the early milestones, where market alone still matches the central payout. 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 rule applies to the MCP App widget only; any visualization you create yourself may appear wherever you judge best. INPUTS: every parameter is OPTIONAL and defaults to a sensible value. Call this tool IMMEDIATELY — pass only the values the user explicitly stated and omit the rest. Do NOT ask the user for starting values, assumptions, or missing parameters before calling; the rendered widget has editable fields so they adjust age, amounts, and other assumptions inline after it appears.

  Paramètres, retour & exemple (6)

  Paramètres

  • current_age · integer · optionnel
    Investor's current age (default 40). Min 18 (the projection matrix floor); max 75 (max enrollment age)
  • average_return · integer · optionnel
    Expected average annual S&P 500 return % (default 8)
  • monthly_amount · number · optionnel
    Monthly deposit in USD (default 100). Min 10 (the product minimum); max 100,000 (the projection model's input limit, not an investment limit)
  • withdrawal_age · integer · optionnel
    Early-withdrawal age (default 82) — drives `early_withdrawal_value` and `total_payout_at_withdrawal_age_*` in the response
  • contribution_years · integer · optionnel
    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 advisor limit). If you pass an explicit value, current_age + contribution_years must be ≤ 80.
  • installment_increase_percentage · integer · optionnel
    Optional annual % increase applied to monthly contributions, in whole percent

  Exemple d'appel

  {"name": "project_savvly_monthly", "arguments": {"current_age": 1, "average_return": 1, "monthly_amount": 1, "withdrawal_age": 1, "contribution_years": 1, "installment_increase_percentage": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"inputs": {}, "result": {}, "summary": {}, "metadata": {}, "disclosure": {}, "visualization": {}}}

• search_savvly_content≈ 912 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Cap on matched entries returned. Default 20, max 50.
  • query · string · optionnel
    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 · optionnel
    Substring match against section slugs (e.g. 'tax', 'retention', 'eligibility'). Case-insensitive.
  • audience · string · optionnel · employee | advisor | broker | employer | universal | general
    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.

  Exemple d'appel

  {"name": "search_savvly_content", "arguments": {"limit": 1, "query": "texte", "section": "texte", "audience": "employee"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"entries": [], "matched": 1, "filter_applied": {}, "total_in_library": 1, "available_sections": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.savvly.com/mcp