Data
i.
Postgres, on speaking terms with your agent.
Query, schema, and migrate any Postgres database with sensible safety rails — read-only by default, escalation requires confirmation.
A weekly almanac of Model Context Protocol servers
With metering, payouts, and one bill in place of forty.
The Stripe MCP turns six lines of agent code into a working payments stack — customers, intents, subscriptions, refunds. It is now the most-used MCP on the marketplace, and it has not had an incident since February.
# claude_desktop_config.json { "mcpServers": { "stripe": { "url": "https://proxy .mcpmeter.com/stripe", "headers": { "Authorization": "Bearer mcpm_live_…" } } } }
Query, schema, and migrate any Postgres database with sensible safety rails — read-only by default, escalation requires confirmation.
Issues, pull requests, code search, and review across an organisation's repositories. Scoped tokens, per-repo permissions.
Independent index. No tracking. Returns ranked snippets ready for retrieval-augmented prompts. Safe-search default on.
Read issues, file new ones, change states, link to commits. Built by Linear; the agent shape mirrors the API exactly.
Block-level access. The agent edits like a person edits — appendable databases, hierarchical pages, comment threads.
Channel-scoped writes. Reply-in-thread by default. Per-workspace consent flow with audit log.
The agent surfaces what's broken before you ask. Group-by-fingerprint, frame-level source context, suspect commit attribution.
Domain-verified senders, scoped templates, hard rate caps. Bounce and spam reports flow back to the agent's context.
List, get, put, presign. Optional automatic content-type sniffing. Bucket-level allow-lists keep the blast radius small.
Numbers are pulled live from the proxy ledger. We do not show vanity metrics. If a column reads zero, it means zero.
Eighteen months in, Model Context Protocol is the lingua franca that let agents stop reinventing wrappers around every API. The registry is full. The community is generous. The README files are excellent. What is missing — what has been missing the entire time — is a billing artery: a way for a developer in Recife to charge a developer in Riga a third of a cent for a useful tool call, monthly, in dollars, without either of them speaking about it.
“The protocol is open. The market for it should be too — fair-priced, fairly split, and instrumented so finely that the publisher and consumer trust the meter without having to argue with it.”
mcpmeter is built to be the artery. We sit, deliberately, in the middle of every paid call: authenticate, meter, forward, charge, and pay out. The platform fee is 20 % of usage — 10 % for the first hundred publishers in. Payouts to creators arrive on the first of each month via Stripe Connect, with a fifty-dollar minimum.
On the consumer side: one key, one bill, one place to set spending caps. We expose the proxy at proxy.mcpmeter.com/{slug}, and we write a usage record for every billable call. The ledger reconciles nightly to Stripe. If we charge you for a call, the publisher was paid for it. If we paid the publisher, you were charged. There is no third version.
Issue 01 ships with forty-two listings; we expect three hundred by autumn. If you have a server worth charging for, the door is open. The middle pages of this issue tell you how.
Publish a server →List your MCP server, choose a per-call price, and we route, meter, bill, and pay out — monthly, via Stripe Connect, fifty-dollar minimum. Founders' rate of 10 % platform fee for the first hundred listings, locked for twelve months.
“The first time we replaced four bespoke billing integrations with one mcpmeter key, our staging environment got quieter. We have not gone back.”
“We published our database MCP on Tuesday, were earning by Wednesday morning, and got our first payout on the first of the next month. The arithmetic was correct to the cent.”
“What I value most: a single page in our procurement portal that says mcpmeter, $1,840 last month, here are the line items. Nothing else looks like that yet.”