
Readfirst
io.github.jeonghun917Published by GitHub account jeonghun917v0.22.3Updated Nov 7, 2026
What to read and check before changing a file: project rules, risks, checks and tests per file.
Overview
Local MCP server that gives a coding agent the project rules, risks, checks and tests tied to a file before it changes that file.
- What you can do
- Read per-file context before editing: rules, risks, checks, tests and callers from the project map
- Scan a checkout for fixed bug shapes such as discarded results or unawaited promise assertions
- Verify before finishing that checks pass and nothing the map ties to the change was left out
- Initialize a first map and wire agents and a pull-request action to it
- When to use it
- Useful when an AI coding agent edits an existing repository and needs team knowledge that imports alone do not show, such as unit conventions, legacy columns to keep, or tests to run after a change.
- Requirements
- Runs as a local process via npm (npx readfirst); needs Node 20 or later and works with any language. It reads the local git checkout and a .readfirst/map.json file committed in the repository. No server, account or model calls are required.
Installation
In SourceWeft
- Open Readfirst in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readfirst
What to read and check before you — or your AI agent — change a file.
Bugs it found that are now fixed upstream: Saleor, Wagtail, n8n, django-allauth. 120 real findings across 44 open-source repositories, reported to 17 projects.
Coding agents can follow imports. What they don't know is what your team knows: "amounts here are in cents", "this table is read by the mobile app, keep old columns", "run the payment e2e after touching this". readfirst keeps that knowledge in one file next to the code and hands it out, file by file, at the moment someone is about to change something.
No server, no account, no model calls. MIT. It reads your git checkout and .readfirst/map.json.
What it caught
On the free side, readfirst shows where your code broke before, from git history, on the first run, no map needed.
The hosted version scans for fixed bug shapes taken from real bugs: a result computed and thrown away, a range check
with no type check, a secret compared with !==, and more. Run over 44 open-source repositories, 616 hits, each one
judged and recorded (real, caveat, false positive, dead code):
- 84 bugs in app code, 21 of them low-severity secret comparisons
- 36 tests that can never fail, every one the same shape:
expect(promise).resolves...with noawaitorreturn, so the test ends before the assertion runs - the false positives are kept on record too; the counts come after tuning on the same repositories, so read them as "what is there", not as precision
Fixed upstream:
- saleor: an "only recalculate what changed" option recalculated every discounted price (saleor/saleor#19984).
- wagtail: a superuser who submits a page for moderation got the moderation email about their own submission (wagtail/wagtail#14790).
- n8n: the RabbitMQ node handed back its channel before the queue bindings were made, and a failed bind escaped as an unhandled rejection; the n8n team fixed it after our issue (n8n-io/n8n#43033).
- django-allauth: a provider callback returned a 500 instead of a clean failure on a non-ASCII value; fixed the day it was reported (f1e06cc).
- mealie: a household safety filter that never applied (mealie#8964) is gone on main since a maintainer's scope fix (mealie#8965).
Still with their maintainers: a Tandoor filter that never applied (TandoorRecipes/recipes#4917), and findings sent privately to other projects, which stay unnamed until they are fixed.
Start
Any language; needs Node 20+.
Commit .readfirst/map.json. Filled maps for real repositories (vercel/ai, cal.com, excalidraw and two more):
examples/.
Everything else (Claude Code plugin and hook, MCP for any agent, Cursor rules, the GitHub Action, the map format,
audit, find, monorepos, pinning a version): the guide.
Hosted
The CLI, hook, MCP server and Action are free and never send your code anywhere. The readfirst-app GitHub App can write the first map for you (free once per account) and, on Pro, keep it in step after merges and comment on pull requests. Details in the guide.
License
MIT
Source: README.md at commit 73c0962
Tools
0Version history
9- v0.22.3LatestNov 7, 2026
- v0.17.1Nov 6, 2026
- v0.16.0Nov 5, 2026
- v0.15.1Nov 5, 2026
- v0.15.0Nov 4, 2026
- v0.14.0Nov 4, 2026
- v0.13.0Nov 3, 2026
- v0.7.0Nov 1, 2026
- v0.6.2Nov 1, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts