Readfirst runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
What to read and check before changing a file: project rules, risks, checks and tests per file.
Nothing serious here today
Today is the operative word: we check Readfirst every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add readfirst -- npx -y readfirst{
"mcpServers": {
"readfirst": {
"command": "npx",
"args": [
"-y",
"readfirst"
]
}
}
}[mcp_servers.readfirst]
command = "npx"
args = ["-y", "readfirst"]{
"mcpServers": {
"readfirst": {
"command": "npx",
"args": [
"-y",
"readfirst"
]
}
}
}{
"servers": {
"readfirst": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"readfirst"
]
}
}
}Alternatives to Readfirst
same job, measured the same wayProves software work: triages failing tests, checks whether a test can fail, and reads migrations.
Read-only tools that check whether code, and the tests that claim it works, are real.
Check, format, run and test Renyi programs; the project map with effects, diffs and chunks.
Make a coding agent prove it: run the repo's real tests, typecheck and lint before it says done.
Check whether a Claude Code skill was tested and whether it works before installing it.
Check, test, prove and review a rowstile policy: access rules for Postgres row-level security
Resolve a developer profile to exactly one project blueprint and return its CI-tested setup recipe.
Tells AI agents which files to test first — churn, coverage, and test mapping as risk scores.
Readfirst — questions
Answers built from our own checks of this server.