com.savvly/savvly vs VETR Proposal
com.savvly/savvly is an MCP server published by savvly.com. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), PyPI (MCP servers)). VETR Proposal is an MCP server published by vetrproposal.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.savvly/savvly | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.103 Downloads/month (npm): 1 219 Downloads/week (npm): 680 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.0.103 Downloads/month (npm): 1 219 Downloads/week (npm): 680 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 1.0.103 Downloads/month (PyPI): 433 Downloads/week (PyPI): 122 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.savvly/savvly | VETR Proposal |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-05 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (vetrproposal.com/mcp/vetr) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/savvly/savvly-mcp | Not stated |
| Changes in the last 7 days (differs) | 3 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-02 |
| Endpoint at the last check (differs) | Responded 10 h ago | Status out of date: last check 37 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.savvly/savvly
Savvly MCP: query fund data, model projections, and compare against alternative retirement products.
VETR Proposal
Federal opportunity, grant and award lookups, VETR scores and proposal drafting.
How to run each
com.savvly/savvly As a remote MCP server
claude mcp add --transport http savvly https://api.savvly.com/mcpVETR Proposal As a remote MCP server
claude mcp add --transport http vetr-proposal https://vetrproposal.com/mcp/vetrCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of VETR Proposal nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: com.savvly/savvly · What it can do: VETR Proposal · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.