Ext Ops Panel
Open dashboard
Comparison

io.github.BlueprintLabIO/tidebase vs science.executable/executable-science

io.github.BlueprintLabIO/tidebase is an MCP server published by BlueprintLabIO. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). science.executable/executable-science is an MCP server published by executable.science. 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

Where each is published
Marketplaceio.github.BlueprintLabIO/tidebasescience.executable/executable-science
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: 0.2.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

io.github.BlueprintLabIO/tidebase vs science.executable/executable-science
Factio.github.BlueprintLabIO/tidebasescience.executable/executable-science
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@tidebase/mcp)Remote server (executable.science/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/blueprintlabio/tidebaseNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

In its own words, on Official MCP Registry:

Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.

science.executable/executable-science

In its own words, on Official MCP Registry:

Read-only research pilot catalogue: task templates, resources, starter studies, capability status.

How to run each

io.github.BlueprintLabIO/tidebase As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio tidebase -- npx -y @tidebase/mcp

science.executable/executable-science As a remote MCP server

Claude Code
claude mcp add --transport http executable-science https://executable.science/api/mcp

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 science.executable/executable-science publish no settings it asks for, so we do not compare settings.

What it can do: io.github.BlueprintLabIO/tidebase · What it can do: science.executable/executable-science · 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.

Where the data comes from: how the catalog is built