io.github.BlueprintLabIO/tidebase
NPM · @TIDEBASE/MCP · SCANNED SEP 22
Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 101 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 595 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.BlueprintLabIO/tidebase MCP server?
io.github.BlueprintLabIO/tidebase runs locally as an npm package, launched with npx -y @tidebase/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tidebase/mcp
claude mcp add blueprintlabio-tidebase -- npx -y @tidebase/mcp
{
"mcpServers": {
"blueprintlabio-tidebase": {
"command": "npx",
"args": [
"-y",
"@tidebase/mcp"
]
}
}
} {
"servers": {
"blueprintlabio-tidebase": {
"command": "npx",
"args": [
"-y",
"@tidebase/mcp"
]
}
}
} codex mcp add blueprintlabio-tidebase -- npx -y @tidebase/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"blueprintlabio-tidebase": {
"type": "local",
"command": [
"npx",
"-y",
"@tidebase/mcp"
],
"enabled": true
}
}
} openclaw mcp add blueprintlabio-tidebase --command npx --arg -y --arg @tidebase/mcp
mcp_servers:
blueprintlabio-tidebase:
command: "npx"
args: ["-y", "@tidebase/mcp"] {
"McpServers": {
"blueprintlabio-tidebase": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@tidebase/mcp"
]
}
}
} assistant mcp add blueprintlabio-tidebase -t stdio -c npx -a -y @tidebase/mcp
{
"mcpServers": {
"blueprintlabio-tidebase": {
"command": "npx",
"args": [
"-y",
"@tidebase/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/@tidebase/mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tidebase_create_run Create a run ~112
Create a new Tidebase run row for a workflow. Note: Tidebase does not execute code — creating a run registers it (with optional input, recovery webhook, and channels); your application must invoke the workflow function with this run id for steps to execute.
| Name | Type | Req | Description |
|---|---|---|---|
| input | – | – | Workflow input, stored with the run |
| recoveryWebhook | string | – | URL Tidebase calls with a signed run.resume payload when the run fails |
| workflowName | string | yes | Workflow name, e.g. generate-report |
No output schema declared.
No examples provided.
tidebase_get_run Get full run detail ~101
Fetch everything Tidebase knows about one run: the run record, checkpointed steps (with resume contracts and failure classification), live state, versioned state streams, parent/child run edges, gates, recovery attempts, channel deliveries, usage records, and the append-only event log. Use to answer "where did this run stop and is it safe to rerun?"
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | Run id, e.g. run_abc123 |
No output schema declared.
No examples provided.
tidebase_get_state_versions Get state version history ~90
Read the versioned state history of a run. A snapshot is a labeled state version; time travel is reading an older version. Filter to one stream or to labeled versions (snapshots) only.
| Name | Type | Req | Description |
|---|---|---|---|
| labeledOnly | boolean | – | Return only labeled versions (snapshots) |
| runId | string | yes | Run id |
| stream | string | – | Limit to one state stream by name |
No output schema declared.
No examples provided.
tidebase_health Check Tidebase server health ~36
Verify the Tidebase server is reachable. Use this first if other tools fail. Configured server: http://localhost:7373
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tidebase_list_runs List recent runs ~52
List the 100 most recent Tidebase runs with workflow name, status, attempt count, and timestamps. Use to find a run id or get an overview of what is running, failed, or awaiting review.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tidebase_resolve_gate Resolve an approval gate ~136
Approve, reject, or cancel a pending human-approval gate. Requires the gate resolveToken (found in the gate record via tidebase_get_run, or in the gate.created webhook payload). Gates resolve exactly once: a second attempt returns a conflict. Only resolve a gate when the human you are assisting has explicitly made the decision.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | Who decided, for the audit record |
| decision | string | yes | The decision |
| gateId | string | yes | Gate id |
| runId | string | yes | Run id the gate belongs to |
| token | string | yes | The gate resolveToken |
No output schema declared.
No examples provided.
tidebase_trigger_recovery Trigger run recovery ~68
Ask Tidebase to dispatch the run's recovery webhook so the owning application re-invokes the workflow. Completed steps replay from checkpoints; only unfinished steps execute. Has no effect unless the run was created with a recoveryWebhook.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | Run id to recover |
No output schema declared.
No examples provided.
What is the io.github.BlueprintLabIO/tidebase MCP server?
io.github.BlueprintLabIO/tidebase is an MCP server listed in the public MCP registry as io.github.BlueprintLabIO/tidebase. Inspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant. This page covers its npm package (@tidebase/mcp).
Is the io.github.BlueprintLabIO/tidebase MCP server safe to use?
io.github.BlueprintLabIO/tidebase scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.BlueprintLabIO/tidebase MCP server expose?
io.github.BlueprintLabIO/tidebase exposes 7 tools: tidebase_health, tidebase_list_runs, tidebase_get_run, tidebase_create_run, tidebase_get_state_versions, and 2 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
Is the io.github.BlueprintLabIO/tidebase MCP server still maintained?
io.github.BlueprintLabIO/tidebase is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.BlueprintLabIO/tidebase MCP server under?
io.github.BlueprintLabIO/tidebase declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.