MCP.Market

seatledger MCP server

by agentwares·io.github.agentwares/seatledger·v0.3.0
No reviews yet

Local ledger of Claude Code and Codex tokens, API-equivalent cost, limits and token-rate changes.

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

full report

Adoption
Growing

0 stars317 downloads/wk

Reviews

Write one

Nobody has reviewed seatledger yet.

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

seatledger tools (4)

write = sends, deletes, buys or posts

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

  • seatledger_plan_compare

    What this machine's last 30 days of Claude Code and Codex work would cost on each coding plan, read from the local transcripts: the Anthropic and OpenAI APIs at list prices; Claude Pro, Max 5x, Max 20x, Team standard and Team premium; ChatGPT Plus and Pro; Codex credits at OpenAI's rate card; and Copilot Pro, Pro+ and Max at GitHub's per-token AI-credit rates. Returns each client's tokens, API-equ

  • seatledger_rate_changes

    Step changes in how this machine's coding-agent requests use tokens, per client and model: tokens per request, cache-read share of prompt tokens, cache writes per cache read, tokens per user turn, the share of Claude Code cache writes made at the 1-hour lifetime, and Codex tokens per 1% of its 5-hour window. Each finding has the date it starts, the client version in use and whether that was its fi

  • seatledger_team_summary

    The hosted seatledger team ledger this machine created or joined (`seatledger team create` or `seatledger team join`): what the team's coding-agent seats and tokens bought, from every developer's pushed daily aggregates. Returns team totals; tables by day, month, developer, model and client; and the rate-change findings feed, each with its date, the developer, the client version and whether that w

  • seatledger_usage_summary

    Tokens and API-equivalent dollars from this machine's Claude Code and Codex transcripts, read locally. With no arguments: today by client and model, the last 7 days by day, progress against limits the user recorded with `seatledger limits set`, and the latest rate-limit readings Codex wrote to its own rollouts. With `since` or `group_by`: one table for that range, grouped by day, project folder, m

Public scan report

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

no findings
  • Code scan5 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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How seatledger compares

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

Safety score
82/100
higher than 63% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
317
more than 82% of 12,191 servers with a package

What its tools let an agent do: 4 read

Install seatledger in Claude Code, Cursor or VS Code

Runs npx -y seatledger on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add seatledger -- npx -y seatledger
Add to Cursor

What the publisher says

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

seatledger

What your coding-agent seats and tokens bought, from your own machine — and when the rate changed.

npx seatledger

The picture is the real output of npx seatledger demo, which runs on synthetic history. It is regenerated by pnpm screenshot and a test fails if it drifts from what the CLI prints.

seatledger reads the transcripts Claude Code and Codex already keep on your machine and tells you:

dropping because writes moved to a shorter cache lifetime, more tokens per turn after a client update, or Codex's own 5-hour window filling faster for the same tokens — with the date and the client version where it starts.

  • tokens and API-equivalent dollars by day, project folder, model and client;
  • how fast you are burning toward limits you set, and when you would reach them at this rate;
  • when the rate changed: the same work suddenly costing more tokens per request, cache reads

No vendor will build that last one: it is an alarm about their own rate. seatledger is MIT, has no telemetry and no runtime dependencies, and needs no account. It makes no network calls unless you create or join a team ledger — and then seatledger push sends daily aggregates only, which seatledger push --dry-run prints in full.

Commands

npx seatledger                                  # today and the last 7 days, your limits, vendor readings
npx seatledger report --since 30d --by project  # --by day | project | model | client, --since 2026-09-01
npx seatledger rates                            # step changes over the last 90 days (--since, --client, --model)
npx seatledger limits set --window 5h --tokens 40M     # or --usd 25; --window weekly; --client codex
npx seatledger limits                           # your limits, burn rate, projected time to each
npx seatledger mcp                              # read-only MCP server on stdio
npx seatledger demo                             # all of the above on synthetic history

# the team ledger (optional; the only commands that send anything)
npx seatledger team create --name "Acme platform"   # a free team for up to 3; prints the invite link
npx seatledger team join <invite link> --as alice   # your key goes to ~/.seatledger/team.json (0600)
npx seatledger push --dry-run                   # exactly what would be sent; sends nothing
npx seatledger push                             # this machine's daily aggregates to the team
npx seatledger team                             #

Every command takes --json, --client claude-code|codex, --claude-dir, --codex-dir, --no-cache and --quiet. Without npm: npx github:agentwares/seatledger runs the same CLI from this repository (it ships its built dist/).

What it reads

Shortened. The full README is on GitHub.

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

seatledger: common questions

Is seatledger MCP server safe?
Mostly: it is graded B (82/100). Read the seatledger safety report
How do I install seatledger?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does seatledger need an API key?
Yes. The registry entry asks for SEATLEDGER_KEY.
Is seatledger maintained?
The last commit was 27 days ago (2026-10-08). The latest release is v0.3.0.
How does seatledger compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from agentwares →