SmartBear MCP vs io.github.BlueprintLabIO/tidebase
SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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.BlueprintLabIO/tidebase |
|---|---|---|
| Official MCP Registry | Listed Version: 0.42.0 Downloads/month (npm): 47 525 Downloads/week (npm): 10 500 Forks (GitHub): 50 Stars (GitHub): 44 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 156 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:8a64acae01b6 Forks (GitHub): 50 Pulls (Docker Hub): 14 374 Stars (Docker Hub): 0 Stars (GitHub): 44 Not marked · First seen |
Not listed |
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.BlueprintLabIO/tidebase |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 44 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 14 374 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 50 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@tidebase/mcp) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 160 | Not published |
| Environment variables it asks for (differs) | 17, secrets among them: 10 | 1, secrets among them: 0 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/smartbear/smartbear-mcp | github.com/blueprintlabio/tidebase |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 400 (11 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
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
io.github.BlueprintLabIO/tidebase
Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.
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.BlueprintLabIO/tidebase As a local MCP server: npm package
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcpCommands 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
The marketplaces of io.github.BlueprintLabIO/tidebase publish no list of tools, so we do not compare tools.
Settings each asks for
Only SmartBear MCP asks for
API_HUB_API_KEY (secret)BEARQ_API_BASE_URLBEARQ_API_TOKEN (secret)BUGSNAG_AUTH_TOKEN (secret)BUGSNAG_ENDPOINTBUGSNAG_PROJECT_API_KEYPACT_BROKER_BASE_URLPACT_BROKER_PASSWORD (secret)PACT_BROKER_TOKEN (secret)PACT_BROKER_USERNAMEQTM4J_API_KEY (secret)QTM4J_AUTOMATION_API_KEY (secret)
Show the remaining 7
QTM4J_BASE_URLREFLECT_API_TOKEN (secret)SWAGGER_API_KEY (secret)SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret)SWAGGER_FUNCTIONAL_TESTING_BASE_PATHZEPHYR_API_TOKEN (secret)ZEPHYR_BASE_URL
Only io.github.BlueprintLabIO/tidebase asks for
TIDEBASE_URL
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.BlueprintLabIO/tidebase · 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. 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.