io.github.GuardBee/reverse-shield vs REA
io.github.GuardBee/reverse-shield is an MCP server published by GuardBee. Marketplaces we read that list it: 1 (Official MCP Registry). REA is an MCP server published by morluto. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 |  io.github.GuardBee/reverse-shield |  REA |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 6.8.0 Downloads/month (npm): 1 546 865 Downloads/week (npm): 519 887 Forks (GitHub): 109 567 Stars (GitHub): 443 471 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 6.8.0 Downloads/month (npm): 1 546 865 Downloads/week (npm): 519 887 Forks (GitHub): 109 567 Stars (GitHub): 443 471 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 | io.github.GuardBee/reverse-shield | REA |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 443 471 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 109 567 (better) |
| Last release (differs) | 2026-11-06 (better) | 2026-10-25 (worse) |
| Where it runs (differs) | On your machine (@guardbee/mcp-reverse-shield) | On your machine (rea-agents) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/guardbee/guardbee-mcp | github.com/morluto/rea |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-27 | 2026-10-11 |
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
io.github.GuardBee/reverse-shield
Audits shipped apps for how easily they can be reverse engineered
REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
How to run each
io.github.GuardBee/reverse-shield As a local MCP server: npm package
claude mcp add --transport stdio reverse-shield -- npx -y @guardbee/mcp-reverse-shieldREA As a local MCP server: npm package
claude mcp add --transport stdio rea -- npx -y rea-agents mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: io.github.GuardBee/reverse-shield · What it can do: REA · 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). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.