Gvnr vs SpendShield
Gvnr is an MCP server published by gvnr.dev. Marketplaces we read that list it: 1 (Official MCP Registry). SpendShield is an MCP server published by felixpg13-glitch. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  Gvnr |  SpendShield |
|---|---|---|
| Official MCP Registry | Listed Version: 1.8.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.8.3 Downloads/month (PyPI): 174 Downloads/week (PyPI): 21 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
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 | Gvnr | SpendShield |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (gvnr.dev/mcp) | On your machine (spendshield) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mightbesaad/gvnr | github.com/felixpg13-glitch/spendshield |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 38 h ago returned HTTP 401 | no remote endpoint we check |
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
Gvnr
Budget & cost control for AI agents — per-agent spend caps + rate limits before each call.
SpendShield
Authorization layer between AI agents and money: ALLOW/APPROVAL/DENY, budgets, audit.
How to run each
Gvnr As a remote MCP server
claude mcp add --transport http gvnr https://gvnr.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
SpendShield As a local MCP server: PyPI package
claude mcp add --transport stdio spendshield -- uvx spendshieldCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Gvnr has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Gvnr · What it can do: SpendShield · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.