whats-running-mcp
Live OS ground truth for a coding agent — agent sessions, listening ports, loaded daemons, load average.
Open source · MIT · read-only · no telemetry
We publish three MCP servers that hand a coding agent the truth about the machine it is working on — what is running, what is loaded, what a checkout is quietly telling it to do. They are free, MIT and read-only, and they are staying that way. Sponsorship is how the maintenance gets paid for without any of that changing.
What you would be sponsoring
whats-loaded-mcp
What eats the context window before the first message — skill descriptions by token cost, duplicate installs, memory-file imports.
Company sponsor slots
Your name where developers install their tooling
Every tier below is placement we control and can be held to — a line in a README, a logo on this page, a mention in release notes. Monthly, cancel by email, no contract.
Listed
$50 / mo
Unlimited slots
Your name and link in the sponsors block of all three MCP server READMEs — the same README npm renders on each package page.
- Name + link in the Sponsors section of whats-running-mcp, whats-loaded-mcp and whats-inherited-mcp
- Name + link on this page
- Carried into the npm package page on the next release of each server
Featured
$250 / mo
4 slots
Logo placement at the top of the sponsors block in all three READMEs, plus a one-line description of what you do.
- Logo + link + one line of copy, top of the Sponsors section in all three READMEs
- Logo + link on this page, above the Listed tier
- Mentioned in the release notes of every server release while sponsoring
- Carried into the npm package page on the next release of each server
Sole
$750 / mo
1 slot
One sponsor, named above the fold. If this tier is taken, no other logo appears higher in the README than yours.
- Logo + link directly under the project description in all three READMEs
- Exclusive — no Featured logos rank above you while this slot is held
- Sole placement on this page
- First look at new servers before they are published, and a say in what gets built next
- Carried into the npm package page on the next release of each server
Before you buy a slot — read this
- There are no sponsors yet. These servers were published recently. You would be the first, and the page will say so honestly to everyone who reads it.
- We do not publish install or download counts here, and we will not estimate them. Current npm download numbers and GitHub traffic are visible publicly on each package page, and we will send you the exact figures before you pay if you ask. Buy the placement on the numbers you verify, not on a claim from us.
- This is early inventory, priced like it. The honest reason to take a slot now is that the price is fixed for as long as you hold it and the placement is uncontested — not because there is an audience waiting.
Current sponsors
No sponsors yet.
This block stays empty until someone real is in it. It will never hold a placeholder logo, a past client, or a company that has not paid.
Individuals
If a server saved you an afternoon
One-off, any amount, no account, no tier, no perk. It goes straight into keeping the servers maintained. You get nothing for it except the servers continuing to exist, which is the entire point.
What the money does
- Keeping whats-running-mcp, whats-loaded-mcp and whats-inherited-mcp maintained, published and MIT
- Issue triage and compatibility work as MCP clients change
- More read-only servers in the same family, published free under the same licence
What it explicitly does not buy
- A feature held back from the free build. There is no pro edition of these servers.
- Telemetry, analytics or any callback of any kind. The servers are read-only and offline.
- A licence change. MIT today, MIT after the sponsorship ends.
- An endorsement. Placement is placement — it is not a claim that we use or recommend the product.
Take the first slot
Email the tier, your logo and one line of copy. Placement goes up within a day of the first payment clearing, and you can see exactly where it lands before you pay — the READMEs are public.