io.github.BlueprintLabIO/tidebase vs Lagaam
io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 1 (Official MCP Registry). Lagaam is an MCP server published by lagaam-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Lagaam |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 134 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.2.5 Downloads/month (PyPI): 284 Downloads/week (PyPI): 199 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 | io.github.BlueprintLabIO/tidebase | Lagaam |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@tidebase/mcp) | On your machine (lagaam) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 18, secrets among them: 1 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/blueprintlabio/tidebase | github.com/lagaam-ai/lagaam |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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.BlueprintLabIO/tidebase
Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.
Lagaam
Stops an agent's Trino or Pinot query before it runs if it costs too much or reads outside its grant
How to run each
io.github.BlueprintLabIO/tidebase As a local MCP server: npm package
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcpLagaam As a local MCP server: PyPI package
claude mcp add --env "LAGAAM_ALLOWED_TABLES=<YOUR_LAGAAM_ALLOWED_TABLES>" --env "PINOT_PASSWORD=<YOUR_PINOT_PASSWORD>" --transport stdio lagaam -- uvx lagaamRequires: LAGAAM_ALLOWED_TABLES, PINOT_PASSWORD (secret)
Commands 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
Only io.github.BlueprintLabIO/tidebase asks for
TIDEBASE_URL
Only Lagaam asks for
LAGAAM_AGENT_NAMELAGAAM_ALLOWED_TABLESLAGAAM_ALLOW_ALL_TABLESLAGAAM_AUDIT_LOGLAGAAM_ENGINELAGAAM_MAX_INTERMEDIATE_ROWSLAGAAM_MAX_RETURNED_ROWSLAGAAM_MAX_ROWSLAGAAM_MAX_SCAN_BYTESLAGAAM_METADATA_TTLLAGAAM_QUERY_TIMEOUTPINOT_BROKER_URL
Show the remaining 6
PINOT_CONTROLLER_URLPINOT_PASSWORD (secret)PINOT_USERTRINO_HOSTTRINO_PORTTRINO_USER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.BlueprintLabIO/tidebase · What it can do: Lagaam · 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.