savvly
savvly is an MCP server published by savvly.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does savvly support the current MCP specification (2026-07-28)?
Not yet confirmed. savvly is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is savvly a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for savvly (as of 2026-08-25).
How do I connect to savvly?
savvly is available via a hosted remote endpoint at https://api.savvly.com/mcp, the package npm:@savvly/mcp-server, the official MCP Registry under com.savvly/savvly, the source repository at https://github.com/savvly/savvly-mcp. Authentication: none. Transports: streamable-http.
What tools does savvly expose?
savvly exposes 8 tools, including get_savvly_product_info, compare_savvly_vs_alternative, project_savvly_lumpsum, project_savvly_monthly, project_retirement_with_savvly, check_savvly_eligibility (last verified 2026-08-25).
Does savvly support MCP revision 2025-11-25?
Yes. savvly supports MCP revision 2025-11-25 (checked 2026-08-25).
When were savvly's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does savvly expose?
8 tools verified.
get_savvly_product_infocompare_savvly_vs_alternativeproject_savvly_lumpsumproject_savvly_monthlyproject_retirement_with_savvlycheck_savvly_eligibilityget_savvly_faqsearch_savvly_content
Savvly MCP: query fund data, model projections, and compare against alternative retirement products.
Which MCP spec revisions does savvly support?
savvly has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source |
How widely adopted is savvly?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for savvly
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 2
- Forks
- 0
- Last pushed
- (40 days ago)
- Created
- Open issues
- 0
- Primary language
- Dockerfile
- License (repository)
- Apache-2.0
- Continuous integration
- None detected
- Tests
- None detected
- Security policy
- None
Package (npm) as of
- Latest version
1.0.92- Last published
- First published
- Releases
- 63
- License (package)
- Apache-2.0
- Maintainers
- 3
- Direct dependencies
- 2
- Unpacked size
- 6.3 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for com.savvly/savvly at version 1.0.88 - lists remote endpoint https://api.savvly.com/mcp and repository https://github.com/savvly/savvly-mcp - accessed
- Endpoint probe of https://api.savvly.com/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 8 tools - accessed
- Endpoint probe of https://api.savvly.com/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 8 tools - accessed