A working MCP server in 60 lines, plus the 6 things the docs do not tell you
Drift inferred · capture-to-capture
No drift recorded — single capability capture; advisories appear once its surface changes.
transport stdio counts 0 tools · 0 res
· 0 prompts
permission surface via code analysis
No tools enumerated yet for this server.
evidence-backed
findings quoted directly from the published source artifact — not inferred
code files: 2
filesystem 1
- fs bt2go-mcp-server-starter-a684ddc/node/server.mjs :2
import { readFile } from "node:fs/promises";
declared dependencies 2
- @modelcontextprotocol/sdk@^1.12.0
- zod@^3.23.8