MESS — the ledger your agents keep

mess.fyi · remote MCP server · https://mess.fyi/api/mcp

MESS is a searchable ledger of your service accounts — which Supabase, which Stripe, which email owns it, which project it belongs to, what it costs — kept current by your coding agents. You wire the server in once; from then on, agents log accounts as they create or find them, search the ledger before provisioning (so you don't end up with a fourth Supabase account for the same job), and flag any account that holds data or moves money with no recorded owner.

The map, not the vault: MESS stores metadata only. There is no field for a secret value, on purpose. Discovery reads env var names and CLI auth state — secret values never move.

What's in this repo

The server is a hosted service and stays closed. Everything client-side lives here, inspectable:

Related MCP server: AgentValet

Setup

Grab a free key at mess.fyi (Settings → Agent keys), then:

Claude Code

claude mcp add --transport http --scope user mess https://mess.fyi/api/mcp \
  --header "Authorization: Bearer mess_sk_YOUR_KEY"

Cursor — ~/.cursor/mcp.json:

{
  "mcpServers": {
    "mess": {
      "url": "https://mess.fyi/api/mcp",
      "headers": { "Authorization": "Bearer mess_sk_YOUR_KEY" }
    }
  }
}

Any other MCP client that speaks streamable HTTP works the same way. There is also a plain REST surface (/api/v1/accounts) with the same keys, for scripts and CI.

The surface

Seven tools, one prompt:

Two things an agent cannot work out for itself, and so never guesses:

• Project boundaries. From a session you see ${PWD##*/} — a directory name. Whether two labels are one project lives in the human's head, and name similarity does not recover it (on the ledger this was built against, 1 of 6 similar-looking clusters was a real match). So groupings come only from a confirmed answer, and rows keep their labels either way — reads resolve, nothing is rewritten.

• Access breadth. From inside a session you can prove a key works; you can never see who else holds one. So no records means nothing recorded — never "nobody else has access."

Optional Claude Code hooks (one paste, served from the app): a session-start brief — every session opens knowing what the current project runs on — and a write-moment nudge that speaks up when a session touches a provider CLI. Only a provider name and repo folder name are ever sent.

Both hooks also live here, versioned: hooks/session-brief.json and hooks/write-nudge.json — the same JSON the app serves, with mess_sk_YOUR_KEY where your key goes. The paste is still the easy path; the repo copies are the inspectable one. Read what runs on your machine before you install it, and when it changes, see the change as a diff. To install from here, merge either file's hooks block into ~/.claude/settings.json and put your key in.

Full disclosure

The handshake instructions the server sends your agent are published verbatim at mess.fyi/mcp — every variant, plus the dig procedure and the hook nudges. If you'd rather your agent didn't volunteer writes, don't wire it in.

That page is also mirrored in this repo, under disclosure/: every variant, the dig, the nudge, as files. npm run check-disclosure fetches the live page and fails if the mirror has drifted — so "published verbatim" isn't a claim you have to take on trust, it's one with history.

Free to 20 accounts. Teams share one ledger (scoped digs, personal stays personal) and add access breadth. Questions: hello@mess.fyi.

License

This repository — the setup docs above — is MIT licensed. It is not the server: MESS itself is a hosted service and its source is not public. What the server sends your agent is, though, published verbatim at mess.fyi/mcp.