Tool-Guardian-Proxy vs io.github.Savirinc/unfragile
Tool-Guardian-Proxy is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Savirinc/unfragile is an MCP server published by Savirinc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  io.github.Savirinc/unfragile | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.11.0 Downloads/month (npm): 150 Downloads/week (npm): 26 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 | Tool-Guardian-Proxy | io.github.Savirinc/unfragile |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-01 |
| Where it runs (differs) | Remote server (tool-guardian-mcp.vercel.app/api/mcp) | On your machine (@unfragile/mcp-server) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/savirinc/unfragile-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (21 h ago) | 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
Tool-Guardian-Proxy
Safety execution proxy protecting clients during tool calls.
io.github.Savirinc/unfragile
Search 2.2M tool actions for agents and robots, every result labelled. Find, verify, passports.
How to run each
Tool-Guardian-Proxy As a remote MCP server
claude mcp add --transport sse tool-guardian https://tool-guardian-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
io.github.Savirinc/unfragile As a local MCP server: npm package
claude mcp add --transport stdio unfragile -- npx -y @unfragile/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Tool-Guardian-Proxy 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: Tool-Guardian-Proxy · What it can do: io.github.Savirinc/unfragile · 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.