io.github.BlueprintLabIO/tidebase vs The Trade Desk MCP Server
io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). The Trade Desk MCP Server is an MCP server published by cesteral. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  The Trade Desk MCP Server |
|---|---|---|
| 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: 1.3.0 Downloads/month (npm): 1 024 Downloads/week (npm): 101 Forks (GitHub): 5 Stars (GitHub): 8 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 | The Trade Desk MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@tidebase/mcp) | On your machine (@cesteral/ttd-mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/blueprintlabio/tidebase | github.com/cesteral/mcp-open-advertising |
| Changes in the last 7 days (differs) | 2 | 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.
The Trade Desk MCP Server
The Trade Desk management — CRUD, GraphQL, bulk ops, and async reports
How to run each
io.github.BlueprintLabIO/tidebase As a local MCP server: npm package
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcpThe Trade Desk MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
The marketplaces of The Trade Desk MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: io.github.BlueprintLabIO/tidebase · What it can do: The Trade Desk MCP Server · 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.