node:sqlite. Nothing to npm install, nothing to break.A toolkit an agent fully owns: coordinate, read code, run safely, remember, read the web, recall β and see what you built. Every tool is zero-dependency, MCP-native, and ships its own live web view.
The curated index, in the llmstxt.org format: what the kit is, what each tool is for, and where to read more. Start here if you are a model.
All 70 MCP tools β every name, every description, every install command β in one fetch. Generated by asking each server tools/list, so it cannot drift.
Every tool's full README concatenated, so a model can ingest the entire kit in one request instead of seven.
βNothing is indexedβ and βyour code does not contain thatβ are the same sentence to a caller
β and could not be more different. An empty store says it is empty, and says how big the haystack was:
0 hits of 0 notes is a misconfigured path; 0 hits of 500 notes is a real answer.
status: "In Progres" β one letter short β used to return []. An agent asks
what is in progress, is told nothing is, and starts work someone else is already doing. Columns, agents
and namespaces are finite, known sets: a filter outside the set is a mistake, and the error lists the
real values.
Ask a question in any directory and nothing is left behind. Opening a store used to create it β so the empty store the tool had just made then answered the question, and the tool invented the evidence for its own answer.
fetch failed is not an error message. It names no cause, suggests no action, and
cannot be told apart from a typo, a dead host, or being offline. Every error here names what went wrong,
where it looked, and the command that fixes it.
MCP tool annotations, on all 67: 37 read-only Β· 7 destructive Β· 10 open-world. A client can tell a search from a delete without calling either. (The spec's defaults are pessimistic β say nothing, and you have declared yourself destructive.)
The whole loop runs on every push, from fresh clones. All 70 tools are called. The UI is looked at, with data ugly enough to break it. A skipped test is a failed test. And every gate has been watched to fail β a gate nobody has seen fail is a gate you are trusting on faith.
node:sqlite. Nothing to npm install, nothing to break.serve command β a live, self-contained dashboard for humans.tokens.json and enforced in CI by iris.