An MCP Server That Remembers Every Trial Your Agent Signed You Up For

keeper — Wed, 19 Aug 2026 13:51:38 +0000

Disclosure: I run scvd.store, a small store for AI agents, and this piece is about one of its free tools.

Every builder carries a quiet, often hidden ledger of AI tools. With new tools for marketing, sales, and development being released seemingly daily, I find myself getting roped into annual subscriptions or paying for things I just wanted to test out. At this rate of change there's no ledger when you're moving fast, so ultimately the ledger becomes your bank statement, with fees you never wanted to pay.

Agents are making this problem worse. If you run Claude, an OpenClaw agent, or anything with a browser and your blessing, tools now get signed up for on your behalf. The ledger gets longer and the forgetting gets faster, because now even the signup memory isn't yours.

The Tab is a new product at scvd.store that IS that ledger, and it's kept where you already work: inside the agent. It's an MCP server, one JSON block to install, and it stores everything in a single human-readable JSONL file on your machine.

json { "mcpServers": { "scvd-tab": { "command": "npx", "args": ["-y", "scvd-tab"] } } }

Log a trial when you (or your agent) start one. Then, at the start of a session, ask whats_due: the most urgent thing is the first line. Ask burn_rollup and you get your monthly number with what it's made of. A trial converting tomorrow reaches you on whatever your agent was doing anyway.

The architectural decision that matters: no credentials

Every subscription tracker before this one wants your bank login or your inbox OAuth. That's the standard architecture: give us the keys, we'll watch the money.

The Tab inverts it. Your agent already reads your mail through a connector it already holds (if not, it's also quite easy to give it a token to an email box just for subscriptions), so the periodic sweep for receipts and renewal notices runs on access that already exists. Card statements? You export the CSV yourself and hand it to reconcile_card_statement. The Tab holds a credential to exactly nothing.

There is no account to breach because there is no account. There's no server to trust because the "server" is a zero-dependency script you can read top to bottom in a sitting, writing to ~/.scvd/tab.jsonl. And export_tab hands everything back, in full, any time. A product that holds your history hostage is the disease; this is the cure practicing its own hygiene.

Warnings that ride the agent

An MCP server can't wake anybody. It only speaks when spoken to. So the clock runs outside (a one-line cron), and open pages ride back on any tool call. You don't open a dashboard; the warning finds you mid-task.

And here's a detail I care about more than is probably healthy: a page handed to an agent is not a page you heard. Agents summarize, truncate, move on. So only acknowledge_pages marks a warning as actually received, and pages that age out unacknowledged get counted against the product as unspoken_pct. The Tab keeps a public score of its own failure to reach you, instead of assuming delivery. Most software assumes away exactly this.

Every number says what it cannot see

burn_rollup never ships a bare figure. It arrives with a coverage block: what fed the number, which parts are estimates (usage-based bills are marked as estimates, never smuggled in as facts), what the last mail sweep couldn't place, and how far the bank's own statement diverged from the tab's picture at last reconcile.

A dashboard that hides its blind spots is just a prettier way of being wrong. If you've ever trusted a spend tracker's total and then met your actual statement, you know the feeling this is designed to kill.

It remembers which doors need a human

This one exists because agents keep hitting the same walls. Every signup can record what the path demanded: agent_native, email_only, phone_required, kyc_required, human_only. So before your agent burns twenty minutes on a signup that dead-ends at a phone-verification wall, check_before_signup can tell it, because somebody (you, three months ago) already hit that wall and the tab wrote it down.

As far as I know, nobody else is collecting this. It's a map of which tools an agent can actually reach unassisted, built as a side effect of ordinary bookkeeping.

Facts and counts, never advice

The Tab will tell you that you trialed four note-taking tools in six months, canceled three, and currently pay for two. It will not say "you have an overlap problem." That sentence belongs to you, or to your agent; the tab's tools are built to be unable to return it. Popularity and history, never judgment.

That's a design rule with teeth elsewhere in the store too (we keep dated observations of services, never scores on operators, for the same reason). Opinions rot. Records don't.

What it is and isn't

Local-first MCP server (scvd-tab on npm), zero dependencies, append-only JSONL you own outright. Free. No account, no telemetry. There's an optional, consent-gated way to contribute anonymized deltas (tool name, category, week, nothing else) to a pooled layer; consent is itself an event in your log, on/off with full audit trail, and nothing leaves the file without it. It doesn't connect to your bank, doesn't want your passwords, and won't cancel anything for you. It remembers, warns, and reconciles. Your money keeps needing you.

Repo (MIT, spec and schema in the open):

seancrecord / scvd-general-store-repo

The trust layer of the x402 economy — free conformance checking of any issuer's signed offers and receipts, settlement attestation, a Bitcoin-anchored corpus, and a general store for AI agents. USDC on Base & Solana, by Record Creative Co. LLC

Sean-Claude Van Damme's General Store

The trust layer of the x402 economy. Independent signed observation of what other people's endpoints, artifacts and payments actually did — conformance audits, week-long watches, settlement attestations, Bitcoin-anchored timestamps. Every verdict ed25519-signed dated, and verifiable offline without asking us, including the gaps we count against ourselves.

Not an escrow, a guarantor, or a dispute court. Those absorb the risk between payment and delivery and need a balance sheet; we observe that gap and sign what we saw. If you are building escrow or adjudication this is the layer underneath you rather than a competitor. That direction was decided and dated on 2026-08-07, in the open — the reversal sits beside what it replaced at scvd.store/becoming.

It is also a small, sincere general store for autonomous AI agents kept by a human out of Oak City, where you're never late. Agents pay in USDC —…

View on GitHub

The Tab lives in the /tab directory; the full product spec is THE_TAB.md at the repo root, and it's honest about what's built versus planned.

If you try it, the thing I most want to hear is which warning reached you and which one aged out unspoken. I'm not too proud to say I'd love feedback. The x402 ecosystem is nascent and I'm dedicated to finding the "General Store" products that are most helpful to users and their agents.

DEV Community: keeper

An MCP Server That Remembers Every Trial Your Agent Signed You Up For

seancrecord / scvd-general-store-repo

The trust layer of the x402 economy — free conformance checking of any issuer's signed offers and receipts, settlement attestation, a Bitcoin-anchored corpus, and a general store for AI agents. USDC on Base & Solana, by Record Creative Co. LLC

Sean-Claude Van Damme's General Store