MCP server health, State of MCP census
Savvly
com.savvly/savvly
Savvly MCP: query fund data, model projections, and compare against alternative retirement products.
Checks
The exact rows akashi check com.savvly/savvly prints, from the 2026-08-03 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | pass | pushed 5d ago |
| package npm | pass | published (1.0.86) |
| package pypi | pass | published (1.0.86) |
| package nuget | skip | Savvly.McpServer not keyless-probeable |
| package oci | skip | ghcr.io/savvly/savvly-mcp-server:1.0.86 not keyless-probeable |
| package mcpb | skip | https://github.com/Savvly/savvly-mcp/releases/download/v1.0.86/savvly-mcp-server.mcpb not keyless-probeable |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 8 tools: get_savvly_product_info, compare_savvly_vs_alternative, project_savvly_lumpsum, project_savvly_monthly, project_retirement_with_savvly, check_savvly_eligibility, get_savvly_faq, search_savvly_content |
| at least one live entrypoint | pass | 4 alive |
| license present | pass | Apache-2.0 |
| spec 2026-07-28 | warn | needs-migration: no server/discover, rejects handshake-free requests, routing headers not enforced |
Spec 2026-07-28 readiness
Verdict: needs-migration(no server/discover; rejects handshake-free requests; routing headers not enforced). Measured against the 2026-07-28 specification (ruleset 2026-07-28-rc, compiled from the draft and re-diffed against the final text with no verdict-bearing rule changed) with read-only, keyless calls; see the ecosystem readiness report for how this server compares.
| Accepts handshake-free calls | no |
| server/discover implemented | no |
| Session independence | yes |
| Routing headers enforced | unknown |
Advisory: negotiates 2025-06-18.
Evidence
Packages
- npm @savvly/mcp-server · published(1.0.86)
- pypi savvly-mcp-server · published(1.0.86)
- nuget Savvly.McpServer · unprobed
- oci ghcr.io/savvly/savvly-mcp-server:1.0.86 · unprobed
- mcpb https://github.com/Savvly/savvly-mcp/releases/download/v1.0.86/savvly-mcp-server.mcpb · unprobed
Remote endpoints
- https://api.savvly.com/mcp
streamable-http · reachable· HTTP 200· initialize_ok
8 tools: get_savvly_product_info, compare_savvly_vs_alternative, project_savvly_lumpsum, project_savvly_monthly, project_retirement_with_savvly, check_savvly_eligibility, get_savvly_faq, search_savvly_content
server.json
validagainst its declared schema
One of 19804 servers in the 2026-08-03 State of MCP census: 15974 healthy (80.7%), 2792 degraded (14.1%), 851 dead (4.3%), 187 unknown (0.9%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check com.savvly/savvlyInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check com.savvly/savvly --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.