MCP servers by theluckystrike
Practical Model Context Protocol servers for people who work inside Claude, Cursor and other MCP clients.
Every server runs locally over stdio, keeps all data on your machine, and has a genuinely useful free tier.
Pro unlocks the limits for a one-time payment: $19 per server or $39 for the bundle, lifetime.
57 servers plus the office-suite aggregator, 46 of them also reachable as a hosted endpoint with no install.
Try a free task in this browser: compare supplier statement open items, review duplicate invoice references, or match an invoice to a PO and receipts. These examples compute locally and send no field values or diagnostic requests.
For the hosted servers, open the connection page, mint a free token and copy the complete URL. A bare endpoint can initialize and list tools but does not authorize tool calls. Local-only products use their extension or source build; the catalogue identifies each supported path.
That is the invoice server answering a real prompt: a client, some hours, a VAT rate, and a numbered PDF at the end.
The table links the demonstrations that are available; some are labeled evidence diagrams rather than client captures.
Choose the install path supported by your server.
- Claude Desktop bundle. Choose the server in the download catalog, download its versioned
.mcpb and open it.
- Hosted, for 46 servers. Open mcp.zovo.one/mcp/connect, mint a free token and copy the ready URL for your server. That URL includes the token; a bare endpoint does not authorize tool calls. Servers without an endpoint use the bundle or source build.
The npm packages are not published. Use a bundle or the source build below rather than an npm package command.
Or clone and build: git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers,
npm install, npm run build. Each server's README has the full 60-second install with every client config.
Buy Pro: https://mcp.zovo.one (keys verify offline with Ed25519; no phone-home).
Hosted endpoints (no install)
46 servers have hosted endpoints. Open the connect page, get a free token and copy the complete URL for the server you need.
The ready URL has the form https://mcp.zovo.one/mcp/<server>/t/<token>. If your client supports headers, the bare endpoint also works with Authorization: Bearer <token>. The bare URL alone can initialize and list tools but refuses tool calls.
Hosted file tools accept inline data/uploads and return temporary download URLs instead of reading your local disk. Read the server-specific setup guide for supported formats. A local install is the path for files on your machine.
Office Suite, Three-Way Match, Duplicate Invoice Check and Supplier Statement Check are local stdio servers. Do not substitute a hosted URL for their executable. See each server page and the client setup guides.
Registry names
The MCP registry listing for these servers uses word-rich names instead of the plain directory
name, for example time-tracker-timesheet-billable-hours instead of time-tracker, or
office-suite-time-invoice-expense-excel-price instead of office-suite: every extra token is a word the
server's own tool descriptions already use, and registry search matches on whole words, so a name built only
from time-tracker was invisible to a search for "timesheet" or "billable hours". The full list, read from
each server's server.mcpb.json:
| Server | Registry name |
|---|
| time-tracker | io.github.theluckystrike/time-tracker-timesheet-billable-hours |
| price-tracker | io.github.theluckystrike/price-tracker-drop-alert-watch |
| spreadsheet | io.github.theluckystrike/excel-spreadsheet-xlsx-csv |
| invoice | io.github.theluckystrike/invoice-pdf-billing-generator |
| expense-tracker | io.github.theluckystrike/expense-tracker-receipts-mileage |
| currency | io.github.theluckystrike/currency-converter-ecb-rates-daily-keyless |
| docx | io.github.theluckystrike/docx-document-generator-proposal-contract-markdown |
| timezone | io.github.theluckystrike/timezone-world-clock-meeting-slots-overlap-ics |
| office-suite | io.github.theluckystrike/office-suite-time-invoice-expense-excel-price |
The old short names are deprecated on the registry; npm package names, directory names and checkout URLs are
unchanged.
Why these servers
The median MCP server on the public registry gets installed and never called again. Looking at what actually gets
used, two things separate the servers people keep: a config snippet that works on the first try, and a visible
demo of the tool actually answering a real prompt before anyone installs it. Both of those are cheap to provide and
most servers skip them -- READMEs bury the config three scroll-lengths down, or show no output at all. These servers
were picked because they replace a task people already do in a spreadsheet, a SaaS dashboard or a browser
tab (tracking time, watching a price, editing a sheet, cutting an invoice, logging a receipt, converting a
currency, drafting a Word document, finding a meeting slot across time zones) with one that runs
entirely on-device: no account, no telemetry, no server-side data at rest (the hosted endpoints are the one
exception, and they say plainly what they keep and for how long). office-suite exists because the most-used
server in this category, measured across the registry, is an aggregator: one install beats thirty-one.
Guides
Also live: 54 client-by-server setup pages (six clients: Claude Desktop, Claude
Code, Cursor, VS Code, Windsurf, Cline, times every server) and 8 head-to-head compare pages
against named competitor MCP servers, sourced from each competitor's own README, GitHub metadata or npm/registry
record.
Validation
Before anything ships: 1,563 unit tests across the servers and the shared license package (protocol smoke
tests over real stdio, plus adversarial cases: bad input, oversized strings, path traversal, concurrent
writers, zero-byte files), a 951-check live validation database run against the built servers and the hosted
worker (data/validation.json, run 50), seven rounds of user-value testing through a real MCP client (one
prompt per conversation, not a unit test; round 7 is cross-server, chaining calls across the whole
office-suite bundle), and four rounds of independent Codex model review of the core build plus two more of the
remote hosted worker. Details: docs/AUDIT.md, docs/CURRENCY_AUDIT.md,
docs/DOCX_AUDIT.md, docs/EXPENSE_AUDIT.md,
docs/TIMEZONE_AUDIT.md, docs/USER_VALUE.md through
docs/USER_VALUE_R7.md, docs/CODEX_REVIEW.md through
docs/CODEX_REVIEW_V4.md, docs/CODEX_REVIEW_REMOTE.md,
docs/CODEX_REVIEW_REMOTE_V2.md, docs/REMOTE_RESULT.md.
npm status
The MCP packages are not published on npm. Use the versioned download catalog, a source build, or the hosted endpoints where available. Earlier npm authentication findings are recorded in docs/NPM_AUTH_RESULT.md; an unpublished package command is not an install path.
Historical access notes
These earlier access findings have not been revalidated in this section. The released bundles, source repositories and hosted setup paths above work without these extra services:
- npm -- publish token is dead; needs
npm login --auth-type=web once, in a browser, from this account.
- Smithery -- CLI and REST are otherwise fully scriptable with a bearer key, but getting that key needs one
browser login:
npx -y @smithery/cli auth login, then open the printed smithery.ai/auth/cli?s=<session>
URL. smithery.yaml is already validated against the CLI schema.
Everything else in this repository -- registry, GitHub, .mcpb release, billing, hosted endpoints, guides,
setup pages, compare pages, Docker MCP catalog PR, Cline marketplace issues, mcpservers.org and mcpmarket.com
submissions -- was completed without a human at the keyboard.
Repository layout: servers/* one package per server, packages/mcp-license shared licensing, billing/ Cloudflare Worker
that sells keys and serves the marketing site (guides, setup pages, compare pages) through Stripe Checkout,
remote/ Cloudflare Worker serving the hosted endpoints, dashboard/ status page, docs/ runbooks.
Built by theluckystrike. https://github.com/theluckystrike Support: [email protected]
