io.github.BlueprintLabIO/tidebase
NPM · @TIDEBASE/MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 51 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @tidebase/mcp
claude mcp add blueprintlabio-tidebase -- npx -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": {
"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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 +31
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +54
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- Licence: Apache-2.0 functional
- 27 Jul 26 26
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@tidebase/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.