savvly-mcp
Related Servers
Alternatives to savvly-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePublic, no-login MCP server exposing SmartMoney77's financial calculators: compound interest, FIRE number, credit-card payoff, emergency fund, inflation, fees and the cost of waiting. Also computes historical "what if I had invested" returns from real yearly price data, and builds deep links and share packs for calculators in 6 localized editions.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for cove-fi, a deterministic retirement and financial-independence projection engine. It lets users run plans, create scenarios, and explore year-by-year net-worth projections through natural language.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.24 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT
- AlicenseAqualityCmaintenanceOfficial MCP server for Agni Folio, a free multi-currency wealth & portfolio tracker. 23 tools for holdings, performance, FIRE planning, crypto P&L, and confirm-gated writes — hosted endpoint with OAuth 2.1, plus a Docker stdio bridge in this repo.4MIT
- AlicenseNot gradedqualityCmaintenanceA stateless MCP server for composing, validating, auditing, and rendering consequential documents from a small semantic model.MIT
TDQS
Scored across 8 tools
The two projection tools (lumpsum vs monthly) are cleanly split by contribution mode, and the full-horizon simulation is distinguishable by its planning-horizon framing. The one real overlap is get_savvly_faq vs search_savvly_content, but the FAQ description explicitly scopes itself as a convenience view of the broader search, which mitigates misselection.
All names are snake_case with the 'savvly' domain token embedded and follow a verb-first pattern (project_, get_, search_, check_, compare_). Minor deviation in token ordering (get_savvly_product_info vs project_savvly_lumpsum) but the verb_noun_resource pattern is predictable.
Eight tools is well within the sweet spot for a product-explainability server, and each covers a distinct need (projections, eligibility, comparison, product facts, Q&A). No padding or redundancy apparent beyond the intentionally scoped FAQ alias.
The surface covers the lifecycle an advisor-facing flow needs: understand the product, check eligibility, compare alternatives, project outcomes, and answer objections. Gaps are minor — there is no way to retrieve current assumptions/rates or persist/share a projection, but agents can work around these.