MCP.Market

Tidebase MCP server

by BlueprintLabIO·io.github.BlueprintLabIO/tidebase·v0.1.1·1 stars
No reviews yet

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

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

1 stars30 downloads/wk

Reviews

Write one

Nobody has reviewed Tidebase yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Tidebase tools (7, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • tidebase_create_runwrite action

    Create a new Tidebase run row for a workflow. Note: Tidebase does not execute code — creating a run

  • tidebase_get_runwrite action

    Fetch everything Tidebase knows about one run: the run record, checkpointed steps (with resume

  • tidebase_get_state_versions

    Read the versioned state history of a run. A snapshot is a labeled state version; time travel is

  • tidebase_health

    Verify the Tidebase server is reachable. Use this first if other tools fail.

  • tidebase_list_runs

    List the 100 most recent Tidebase runs with workflow name, status, attempt count, and timestamps.

  • tidebase_resolve_gate

    Approve, reject, or cancel a pending human-approval gate. Requires the gate resolveToken

  • tidebase_trigger_recovery

    Ask Tidebase to dispatch the run's recovery webhook so the owning application re-invokes the

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 97 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Tidebase compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 68% of 4,460 AI and agents servers
Tools
7
the typical AI and agents server has 6
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 50% of 2,711 AI and agents servers
Downloads a week
30
more than 17% of 1,538 AI and agents servers with a package

What its tools let an agent do: 5 read · 2 change

Install Tidebase in Claude Code, Cursor or VS Code

Runs npx -y @tidebase/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add tidebase -- npx -y @tidebase/mcp
Add to Cursor

What the publisher says

From the Tidebase repository's README, as published. We do not edit it. Read it on GitHub

Tidebase

Agent auth and credential brokering for AI agents, with checkpoints, queues, schedules, and approval gates. In your own Postgres.

Quick start · API · Storage contract · Scope

Tidebase gives your AI agents an identity and a vault. When an agent calls an API, the call goes through Tidebase, which injects the credential, so the agent and the model never see the key. You can scope it, audit it, and revoke it.

It also keeps the durable parts: checkpoints, live state, queues, schedules, and approval gates, all in your own Postgres. Your code still runs in your app, worker, or job process; Tidebase does not run it. So "this run died at step 7, is it safe to rerun?" has an answer, and "the agent has my GitHub token in plaintext" stops being true.

Docs: · Community: Discord · For AI assistants: /llms.txt

Why Tidebase

Agent products usually grow the same operational plumbing:

  • per-agent identity instead of one shared API key
  • a vault for third-party secrets and OAuth tokens
  • a way to call APIs without handing the secret to the model
  • status tables for runs and steps
  • checkpoint blobs for partial progress
  • retry flags and manual-review states
  • progress streaming to the UI
  • approval gates for risky actions
  • token and cost ledgers
  • webhook glue for recovery and external review surfaces

Tidebase packages that layer around your existing code, plus a credential broker so agents act on real services without holding the keys. It does not run your code (your runtime stays yours), and it is not an LLM proxy or a hosted worker runtime.

Quick Start

Fastest path (no Node needed), prebuilt server image:

docker compose --profile server up -d   # Postgres + ghcr.io/blueprintlabio/tidebase on :7373

Then point any SDK at http://localhost:7373 (npm i @tidebase/sdk or pip install tidebase).

Dev setup (server + Studio from source):

Start Postgres:

docker compose up -d postgres

Install dependencies:

pnpm install

Run the server and Studio:

pnpm dev
  • Server: http://localhost:7373
  • Studio: http://localhost:5173

Run the example workflow:

pnpm example

Force a failure after two completed checkpoints:

FAIL_WRITE=1 pnpm example

Copy the run id from Studio or the API, then resume:

TIDEBASE_RUN_ID=run_xxx pnpm example

The plan and fetch-sources steps are returned from checkpoints. Only write-report executes again.

Agent auth and credential brokering

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Tidebase: common questions

Is Tidebase MCP server safe?
Mostly: it is graded B (83/100). Read the Tidebase safety report
How do I install Tidebase?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Tidebase need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Tidebase maintained?
The last commit was 135 days ago (2026-06-22). The latest release is v0.1.1.
What can I use instead of Tidebase?
Servers from other publishers that do the same job: agent-device MCP server, HOL Guard MCP server and IWE (iwe.md) MCP server.
How does Tidebase compare with other AI and agents MCP servers?
safety score 83/100 (higher than 68% of 4,460 AI and agents servers); tools 7 (the typical AI and agents server has 6); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Tidebase

Same job from other publishers: the closest match first, then the best rated.

  • agent-device
    Let AI agents inspect, control, and debug real iOS, Android, desktop, and TV apps
    A
  • HOL Guard
    Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
    A
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • Orcareplay
    Read, replay and fork recorded coding-agent runs.
    A