SmartBear MCP vs io.github.chrischall/simplisafe-mcp
SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.chrischall/simplisafe-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (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 |  SmartBear MCP |  io.github.chrischall/simplisafe-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.43.0 Downloads/month (npm): 34 553 Downloads/week (npm): 6 200 Forks (GitHub): 50 Stars (GitHub): 44 Not marked · First seen |
Listed Version: 1.4.0 Downloads/month (npm): 1 255 Downloads/week (npm): 196 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Removed on 2026-11-07 Version: sha256:8a64acae01b6 Forks (GitHub): 50 Pulls (Docker Hub): 15 119 Stars (Docker Hub): 0 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 1 255 Downloads/week (npm): 196 Forks (GitHub): 0 Stars (GitHub): 0 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 | SmartBear MCP | io.github.chrischall/simplisafe-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 44 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 50 (better) | 0 (worse) |
| Last release (differs) | 2026-11-03 (worse) | 2026-11-04 (better) |
| Where it runs (differs) | Remote server (bugsnag.mcp.smartbear.com/mcp) | On your machine (simplisafe-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 17, secrets among them: 10 | 3, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/smartbear/smartbear-mcp | github.com/chrischall/simplisafe-mcp |
| Changes in the last 7 days (differs) | 3 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 41 h ago returned HTTP 400 | 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
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
io.github.chrischall/simplisafe-mcp
Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks
How to run each
SmartBear MCP As a remote MCP server
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcpRequires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)
io.github.chrischall/simplisafe-mcp As a local MCP server: npm package
claude mcp add --env "SIMPLISAFE_REFRESH_TOKEN=<YOUR_SIMPLISAFE_REFRESH_TOKEN>" --transport stdio simplisafe-mcp -- npx -y simplisafe-mcpRequires: SIMPLISAFE_REFRESH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SmartBear MCP 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
Only SmartBear MCP asks for
BEARQ_API_BASE_URLBEARQ_API_TOKEN (secret)BUGSNAG_AUTH_TOKEN (secret)BUGSNAG_PROJECT_API_KEYPACT_BROKER_BASE_URLPACT_BROKER_PASSWORD (secret)PACT_BROKER_TOKEN (secret)PACT_BROKER_USERNAMEQTM4J_API_KEY (secret)QTM4J_AUTOMATION_API_KEY (secret)QTM4J_BASE_URLREFLECT_API_TOKEN (secret)
Show the remaining 5
SWAGGER_API_KEY (secret)SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret)SWAGGER_FUNCTIONAL_TESTING_BASE_PATHZEPHYR_API_TOKEN (secret)ZEPHYR_BASE_URL
Only io.github.chrischall/simplisafe-mcp asks for
SIMPLISAFE_REFRESH_TOKEN (secret)SIMPLISAFE_TOKEN_CACHESIMPLISAFE_TOKEN_FILE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: SmartBear MCP · What it can do: io.github.chrischall/simplisafe-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.