Nine MCP servers, zero dependencies: what we learned writing the protocol by hand
Published · 6 min read
Disclosure: this article is by the team behind Ezkielyna, an independent AI API gateway. Three of these servers call it; the other six don't need it at all. All nine are MIT-licensed and on GitHub under EzkielynaGroup. Drafted with AI assistance and edited by the team.
We shipped nine MCP servers in November 2026. Each one is a single .mjs file with no runtime dependencies: no MCP SDK, no zod, no HTTP client. Node 18+ and the standard library only.
That was a deliberate choice, and not always the right one. Here is what it cost, what it bought, and the protocol details we only learned by writing them ourselves.
The nine servers
| Server | What it does | Needs a key? | Lines | Tests |
|---|---|---|---|---|
| ezkielyna-mcp | Ask or compare other models, web search, balance | yes | 657 | 13 |
| ezkielyna-image-mcp | Generate and edit images | yes | 545 | 12 |
| ezkielyna-audio-mcp | Text to speech, transcription | yes | 591 | 9 |
| ai-model-status-mcp | Live per-model status, uptime and price from a public feed | no | 658 | 15 |
| mcp-bmkg | Indonesian earthquake and weather data (BMKG open data) | no | 480 | 13 |
| mcp-hari-libur-indonesia | Indonesian public holidays, working-day maths | no | 633 | 13 |
| mcp-wilayah-indonesia | 91,599 Indonesian region codes, offline | no | 548 | 11 |
| mcp-qris | Parse and validate QRIS payloads, set amounts, render SVG | no | 973 | 19 |
| mcp-rupiah | Rupiah formatting, number-to-words, Indonesian VAT | no | 767 | 18 |
That is 5,852 lines and 123 tests in total, counted on 12 Nov 2026. Every server is on npm and in the MCP Registry (registry.modelcontextprotocol.io) under io.github.EzkielynaGroup/*.
Why zero dependencies?
npx -ycold start. Most people install an MCP server with a line likenpx -y mcp-rupiahin their client config. Every dependency is a download on the first run and another place for a version conflict. Our packages ship 4 files each;mcp-wilayah-indonesiaships 6 because it bundles its data.- Auditability. An MCP server runs with the user's permissions, next to their files and keys. A reviewer can read one 600-line file. Nobody reads a
node_modulestree. - Supply chain. Agent tool registries have already had malware incidents. The Hacker News reported 341 malicious skills on ClawHub in February 2026. Fewer packages means fewer ways in.
- Longevity. These servers do small, stable jobs. We don't want to bump them every time a transitive dependency publishes a major version.
The costs are real:
- You write and maintain JSON-RPC handling yourself.
- You track protocol versions yourself.
- You get no schema-validation library.
For a server with OAuth, HTTP transport, sampling or resources that change, use the MCP SDK. For a stdio server with a handful of tools, writing it by hand was fine.
The protocol, the parts that bit us
stdout is sacred
On the stdio transport, stdout carries JSON-RPC and nothing else. One console.log("starting…") corrupts the stream, and the client typically shows a vague "server disconnected" error. All our logging goes to stderr through a small log() helper, and tests fail if stdout carries anything that isn't JSON.
One message per line, with limits
We read stdin with readline and parse each line as one message (or a batch array). We reject lines over 1 MB with a JSON-RPC error instead of trying to parse them, so a runaway client can't make us buffer forever.
Notifications don't get answers
A message with no id is a notification. Answering one is a protocol error that some clients log loudly. The handler returns early when id is missing.
Negotiate the version, don't hard-code it
During initialize, the client sends the protocol version it wants. We keep a list of versions we know (2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05) and echo the client's choice if it is on the list, otherwise our default. Hard-coding one version broke an older client in testing.
Use the error codes the spec gives you
| Situation | Response |
|---|---|
| Unknown method | JSON-RPC error -32601 |
| Unknown tool name | JSON-RPC error -32602 |
| Tool ran but failed (bad input, upstream down) | A normal result with isError: true and a short, actionable message |
| Unparseable line | -32700 with id: null |
The isError distinction matters. An error the model can read lets it fix its own call: "Format angka tidak dikenali / unrecognised digit grouping" tells it to retry with a clean number. A protocol error just stops the turn. Since our users are mostly Indonesian, messages are in Indonesian and English, and they never contain a stack trace.
Annotate your tools
Every tool has a JSON Schema inputSchema with descriptions, plus annotations such as readOnlyHint, destructiveHint, idempotentHint and openWorldHint. Clients use these to decide what needs confirmation. A pure formatter like format_rupiah is read-only and closed-world; an image generator is not.
Testing without the internet
Every test suite runs with node --test and no network:
- The test file starts a local mock HTTP server with recorded, trimmed fixtures.
- It spawns the MCP server over stdio and points it at the mock through an environment variable.
- It speaks JSON-RPC to it: handshake,
tools/list, every tool, and every error path. - CI runs the suites on Node 18, 20 and 22.
A few tests we're glad we wrote:
- mcp-qris: the CRC check uses the standard check value (CRC of
"123456789"is0x29B1). The QR encoder was cross-checked against macOS's own QR decoder on 268 of 268 generated symbols. - mcp-hari-libur-indonesia: runs the date maths under four different machine time zones. Holiday date bugs love UTC-vs-local mistakes.
- mcp-rupiah: a number-to-words-to-number round trip over 300+ numbers, using BigInt so large amounts never drift.
- ezkielyna-mcp: the first live run with a real key showed that keys can carry a model allowlist. The server then answered "no access to model" with an unhelpful message, so we rewrote the message and added a test.
Things that aren't about code
- Data licences come first. The region codes come from an MIT-licensed upstream dataset, and the licence ships with the package. Holiday data was compiled from the government decree pages, and the README says it was not compared against the signed PDFs. BMKG data is attributed in every answer. If you can't redistribute a dataset, fetch it at runtime and attribute it.
- Wording is a feature. We renamed one tool to
lowest_price_modelsbecause its first name made a claim about the whole market. Its output now says "lowest listed price on this gateway", which is what it actually measures. - Filter what you publish. The status server reads a public model feed and drops some model ids before listing them. Decide your filters before your data is in someone's screenshot.
- Paid tools need caps. The three servers that spend money have a per-session call cap (for example
EZKIELYNA_MAX_CALLS, default 50) and amax_tokenscap. An agent in a loop should hit a wall, not your balance. - The registry wants its own file.
server.jsonfollows the registry schema, and its description is limited to 100 characters. Write it once and validate it in CI.
Should you do this?
Write it by hand if:
- the server is stdio-only,
- it has fewer than about ten tools,
- it is stateless or file-backed,
- and you care about install speed and auditability.
Use the SDK if you need HTTP transport, auth, resources, prompts, sampling, or you have more than one person maintaining it.
Our reference shape (one file, the initialize/tools/list/tools/call/ping handler, and the mock-server test harness) is in any of the repos. mcp-rupiah is the smallest offline one to read.
Install one in Claude Code to try it:
claude mcp add rupiah -- npx -y mcp-rupiahThen ask: "Write Rp1.250.000 in Indonesian words and add 11% effective VAT."
Sources
- Repos: https://github.com/EzkielynaGroup (line and test counts from the repos on 12 Nov 2026)
- MCP specification: https://modelcontextprotocol.io/specification
- MCP Registry: https://registry.modelcontextprotocol.io/
- The Hacker News on ClawHub (Feb 2026): https://thehackernews.com/2026/02/researchers-find-341-malicious-clawhub.html
Ezkielyna is an independent API gateway: one OpenAI- and Anthropic-compatible key for many AI models, prepaid with QRIS, USDT or Binance Pay, no credit card needed. It is not affiliated with the companies that make the models.