Tidegap MCP server
io.github.tidegap/tidegap·v0.20.0·1 starsRuns non-urgent LLM tasks at the cleanest grid hour before a deadline, via Batch APIs when allowed.
not scanned yet
1 stars
Reviews
Write oneNobody has reviewed Tidegap yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Tidegap tools
No tool declarations could be read from the package source. They show once the server is installed.
How Tidegap compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 65% of 4,460 AI and agents servers
- GitHub stars
- 1
- more than 50% of 2,711 AI and agents servers
Release history: 3 versions in the registry since 2026-10-16, latest 2026-11-03, typically one every 16 days.
Install Tidegap in Claude Code, Cursor or VS Code
Runs npx -y @tidegap/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add tidegap -- npx -y @tidegap/mcp
What the publisher says
From the Tidegap repository's README, as published. We do not edit it. Read it on GitHub
Tidegap
Run non-urgent LLM tasks at the cleanest grid hour before your deadline.
Tidegap takes the LLM tasks your agent does not need right now, runs them at the lowest-carbon grid hour before a deadline you set, and sends them through the provider Batch API when the deadline allows.
- Picks the dispatch hour from a live 72-hour grid carbon-intensity forecast: 5 real-data feeds, 31 regions (measured, counted in code).
- Routes work with a deadline over 24 hours through the Anthropic and OpenAI Batch APIs, at 50 % of the sync list price (projected, provider list price).
- Writes a signed carbon receipt per task to a local SQLite ledger. tidegap verify checks it offline.
npm install @tidegap/core # TypeScript / Node
pip install "tidegap[anthropic,openai,signing]" # Python 3.11+
claude plugin marketplace add tidegap/tidegap && claude plugin install tidegap # Claude Code
npx -y @tidegap/mcp # any other MCP host// save as plan.mjs, run: node plan.mjs (GB uses the free UK feed, no API key)
import { recommendWindow, ukCarbonIntensityFeed } from "@tidegap/core";
const deadline = new Date(Date.now() + 24 * 3600 * 1000).toISOString();
const plan = await recommendWindow({ region: "GB", deadline }, { feed: ukCarbonIntensityFeed(), rng: () => 0 });
console.log(plan.scheduledFor, plan.intensityGCo2PerKwh, plan.band);
// 2026-10-16T11:00:00.000Z 66 very_clean (forecast value on 2026-10-15; yours will differ)import asyncio; from datetime import datetime, timedelta, timezone
from tidegap import recommend_window, uk_carbon_intensity_feed
deadline = datetime.now(timezone.utc) + timedelta(hours=24)
plan = asyncio.run(recommend_window(region="GB", deadline=deadline, feed=uk_carbon_intensity_feed(), rng=lambda: 0))
print(plan.scheduled_for, plan.intensity_g_co2_per_kwh, plan.band)
# 2026-10-16T11:00:00.000Z 66 very_clean (forecast value on 2026-10-15; yours will differ)Without rng, Tidegap picks at random among the cleanest band of near-equal hours, so repeated runs spread load and can return different hours; an rng that returns 0 gives the strict minimum.
Proof: one real run (GB, 2026-09-30, live National Grid ESO forecast). Forecast peak 183 gCO2/kWh, recommended window 88 gCO2/kWh: about 52 % lower, for this run only (forecast, projected). The test task had a 5-minute deadline, so it ran at once; its signed receipt records 158 gCO2/kWh (measured). Raw output and reproducer · every number and its source
In an agent: in Claude Code, /tidegap:defer "Summarize today's notifications" --by 4h. In any other MCP host, the agent calls recommendwindow and scheduletask (10 MCP tools, 13 hosts — host configs).
Renamed from Ebb AI
Until 0.17 this project was Ebb AI (@ebb-ai/*, ebb-ai on PyPI, the ebb command). 0.18.0 renames it to Tidegap, because "Ebb" conflicts with an existing software trademark. Your queue, receipts, signing key and daemon keep working. The old names still work for one release (0.18) and stop in 0.19.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Tidegap: common questions
- Is Tidegap MCP server safe?
- Mostly: it is graded B (82/100). Read the Tidegap safety report
- How do I install Tidegap?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Tidegap need an API key?
- Yes. The registry entry asks for
ANTHROPIC_API_KEY,OPENAI_API_KEY,TIDEGAP_EIA_API_KEY,TIDEGAP_ENTSOE_SECURITY_TOKENand 2 more. - Is Tidegap maintained?
- The last commit was 19 days ago (2026-10-16). The latest release is v0.20.0.
- What can I use instead of Tidegap?
- Servers from other publishers that do the same job: Decionis MCP server, IWE (iwe.md) MCP server and Orcareplay MCP server.
- How does Tidegap compare with other AI and agents MCP servers?
- safety score 82/100 (higher than 65% of 4,460 AI and agents servers); github stars 1 (more than 50% of 2,711 AI and agents servers). Full comparison.
Alternatives to Tidegap
Same job from other publishers: the closest match first, then the best rated.
- DecionisAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- IWE (iwe.md)Markdown knowledge base as agent memory. Runs against the notes directory it is started in.not reviewedEstablishedA
- OrcareplayRead, replay and fork recorded coding-agent runs.not reviewedEstablishedA