io.github.BlueprintLabIO/tidebase vs Execute data-observability-mcp
io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 1 (Official MCP Registry). Execute data-observability-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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.BlueprintLabIO/tidebase | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 156 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 2.0.0 No figure published 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.BlueprintLabIO/tidebase | Execute data-observability-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@tidebase/mcp) | Remote server (api.m2mcent.com/data-observability-mcp/sse) |
| Transport (differs) | stdio | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/blueprintlabio/tidebase | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (1 h ago) |
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.BlueprintLabIO/tidebase
Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.
Execute data-observability-mcp
Premium agentic endpoint for data-observability-mcp.
How to run each
io.github.BlueprintLabIO/tidebase As a local MCP server: npm package
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcpExecute data-observability-mcp As a remote MCP server
claude mcp add --transport sse data-observability-mcp https://api.m2mcent.com/data-observability-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"Requires: Payment-Signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Execute data-observability-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
The marketplaces of Execute data-observability-mcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.BlueprintLabIO/tidebase · What it can do: Execute data-observability-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.