mypowers vs SAM.gov
mypowers is a plugin bundle for AI coding tools published by poulrohan23. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SAM.gov is an MCP server published by 1102tools.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). 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 |  mypowers |  SAM.gov |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 6378fc4 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.18 Downloads/month (PyPI): 638 Downloads/week (PyPI): 102 Forks (GitHub): 10 Stars (GitHub): 31 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.0.18 Downloads/month (PyPI): 638 Downloads/week (PyPI): 102 Forks (GitHub): 10 Stars (GitHub): 31 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 | mypowers | SAM.gov |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 31 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 10 (better) |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 20 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/poulrohan23/mypowers | github.com/1102tools-dev/federal-contracting-mcps |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days 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
mypowers
Zero-trust military-grade AI co-founder OS with progressive FULL/PARTIAL/BASIC security, Fortress Bible audit trail, and native hooks
SAM.gov
SAM.gov readiness, entities, exclusions, opportunities, awards, hierarchy, and subawards. 20 tools.
How to run each
mypowers As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mypowers@claude-communitySAM.gov As a remote MCP server
claude mcp add --transport http sam-gov-mcp https://sam.1102tools.com/mcpRequires: SAM_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SAM.gov has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of mypowers nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of mypowers publish no settings it asks for, so we do not compare settings.
What it can do: mypowers · What it can do: SAM.gov · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.