General Tools
savvly.com
Provides information, comparisons, and retirement projections for the Savvly longevity benefit fund.
ENDPOINT 1
https://api.savvly.com/mcp
MCP server metadata
- Name
- savvly
- Version
- 1.0.93
Savvly's MCP server. Do not use emojis or emoticons in any response. Present all figures as illustrative projections, not guarantees. When the user asks what Savvly is (or for an overview), or to compare Savvly with alternatives, call get_savvly_product_info or compare_savvly_vs_alternative respectively — do not answer from memory; they return authoritative data and render an interactive card.
Known tools 8
get_savvly_product_infoGet 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.
Inferred read-onlycompare_savvly_vs_alternativeGet 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.
Inferred read-onlyproject_savvly_lumpsumRetirement projection for a lump-sum investment in the Savvly Longevity Benefit.
Inferred read-onlyproject_savvly_monthlyRetirement projection for monthly contributions to the Savvly Longevity Benefit over a number of years.
Inferred read-onlyproject_retirement_with_savvlyFull retirement simulation showing the projected savings trajectory WITH and WITHOUT a Savvly allocation across the planning horizon (current_age → life_expectancy).
Inferred read-onlycheck_savvly_eligibilityCheck if a person is eligible to invest in the Savvly Longevity Benefit.
Inferred read-onlysearch_savvly_contentSearch 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.savvly]
url = "https://api.savvly.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"savvly": {
"type": "http",
"url": "https://api.savvly.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: savvly
Remote MCP URL: https://api.savvly.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"savvly": {
"url": "https://api.savvly.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"savvly": {
"type": "http",
"url": "https://api.savvly.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "savvly",
"transport": "streamable-http",
"url": "https://api.savvly.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.