app.zenable/zenable vs io.github.sparkvibe-io/GuardianShield
app.zenable/zenable is an MCP server published by zenable.app. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.sparkvibe-io/GuardianShield is an MCP server published by sparkvibe-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  app.zenable/zenable |  io.github.sparkvibe-io/GuardianShield |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 No figure published Not marked · First seen |
Listed Version: 1.2.1 Downloads/month (PyPI): 93 Downloads/week (PyPI): 21 Forks (GitHub): 2 Stars (GitHub): 3 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 | app.zenable/zenable | io.github.sparkvibe-io/GuardianShield |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.zenable.app) | On your machine (guardianshield) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/sparkvibe-io/guardianshield |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days 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
app.zenable/zenable
Zenable cleans up sloppy AI code and prevents vulnerabilities with deterministic guardrails
io.github.sparkvibe-io/GuardianShield
AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs
How to run each
app.zenable/zenable As a remote MCP server
claude mcp add --transport http zenable https://mcp.zenable.app/io.github.sparkvibe-io/GuardianShield As a local MCP server: PyPI package
claude mcp add --transport stdio guardianshield -- uvx guardianshieldCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only app.zenable/zenable 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
The marketplaces of app.zenable/zenable publish no settings it asks for, so we do not compare settings.
What it can do: app.zenable/zenable · What it can do: io.github.sparkvibe-io/GuardianShield · 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.