Of the 30 servers in this repository, 28 make no network call of any kind. Two do, and both only because the thing they answer lives on someone else's server: the currency server fetches European Central Bank reference rates, and the price tracker fetches the shop page whose price you asked about. Everything else reads and writes files on your machine and talks to nothing.
| Network calls | Servers |
|---|---|
| None | time-tracker, spreadsheet, invoice, expense-tracker, docx, timezone, resume, recurring, clauses, calendar, pdf, image, bank-statement, kanban, quotes, barcode, zip, billing-docs, deposits, per-diem, asset-register, statement-of-account, cash-book, amortization, petty-cash, work-order, catalogue, change-order |
| Fetches a public rate table | currency (ECB reference rates, cached locally) |
| Fetches a page you name | price-tracker (the product page you asked about) |
An MCP server runs as a process on your machine with whatever access you gave it, and the tools it exposes are called by a model rather than by you. If the server also has a network connection, the data flowing through it can leave, and no amount of reading the README will tell you it did not. Cutting the network is the only check that does not depend on trust.
These servers are also unmetered offline. There is no license server to phone: a Pro key is an Ed25519 signature the server verifies locally, so an activated install works on a plane and stays activated. There is no telemetry endpoint and no usage counter that needs to reach anything.
On macOS, Little Snitch or the built-in firewall in block-all mode will show you. On Linux:
sudo unshare -n node /path/to/mcp-servers/servers/invoice/dist/index.jsThat runs the server in a network namespace with no interfaces. Drive it from a client and every
tool on the invoice server still answers. Try the same with the currency server and
rates_latest fails, which is the expected and honest result: it needs the ECB.
The other check is the source. Every server is TypeScript in servers/<name>/src
in a public repository, and a grep for fetch, http or https
across a server's source is a five-second audit that does not require reading any of it.
Under ~/.local/share/mcp-servers/<server>/, or the platform equivalent, as plain
JSON. You can read it with any editor, back it up with anything, and delete it by deleting the folder.
The file-handling servers, spreadsheet, pdf, image and zip, keep nothing at all beyond a recent-files
list: they work on the files you name and leave the results where you asked for them.
The one exception to all of this is the hosted endpoints. mcp/connect gives you a URL instead of an install, and a hosted server necessarily sees what you send it. That is a genuine trade and the page says which one you are making.
Partly. It caches what it fetched under ~/.local/share/mcp-servers/currency/, so a conversion at a rate already in the cache answers with no network. A rate it has never seen cannot be invented, and it says so rather than guessing.
No. The key is verified with an offline Ed25519 signature check inside the server. There is no activation server, no seat count and no expiry ping. An air-gapped machine activates from the key string alone.
It fetches the one product page URL you give it and reads the price out of JSON-LD, microdata, Open Graph tags or common price markup. It follows no links, crawls nothing, and refuses a redirect that leaves the product page rather than reporting the price of whatever it landed on. Pages that block bots are handled by typing the price in by hand.
Yes, if you get the code there. Clone and build on a connected machine, copy the repository directory across, and the built dist runs. The .mcpb bundle is a single self-contained file and copies across just as easily.
All MCP servers and prices · All guides · Buy the bundle $39