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.
A specimen of how a payments MCP would be presented on mcpmeter — the standfirst, the publisher's own copy, the configuration block, and the transparent meter. Real listings will replace this once publishers begin onboarding.
# claude_desktop_config.json { "mcpServers": { "stripe": { "url": "https://proxy .mcpmeter.com/stripe", "headers": { "Authorization": "Bearer mcpm_live_…" } } } }
A note: these are servers we want to see metered. None are yet listed. The Index will show real listings — with publisher-set prices and live ledgers — as publishers join.
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.
The proxy sits in front of the publisher's MCP. It authenticates, forwards, and records. Nothing more — and we keep the proxy code open so the meter can be inspected.
Once traffic flows, this section will surface live ledger figures. Until then, the mechanics are the story.
Cached in Redis, validated in a few milliseconds. Revoked, over-cap, or unknown keys never reach the upstream.
Pass-through. We do not buffer the body. We do not transform the response. The publisher's MCP behaves exactly as if the agent called it directly.
Slug, tool name, status, byte counts, duration — never bodies. The ledger reconciles to Stripe nightly. Publishers are paid on the first; consumers are billed at month's end.
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 is the design. The marketplace itself opens to publishers first; consumer onboarding follows. 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 platform's job is not to add features to MCP — it is to count calls correctly, charge a sensible price, and send the publisher their share. Every other thing should bend to that.
We do not pick winners. The publisher sets the per-call price. The platform takes a fixed percentage; the rest is paid out monthly to a Stripe Connect account.
The proxy is open source so the meter can be read, not just trusted. The ledger reconciles to Stripe nightly. If we charge for a call, the publisher was paid for it. There is no third version.