io.github.jeonghun917/readfirst
NPM · READFIRST
What to read and check before changing a file: project rules, risks, checks and tests per file.
Available components
Last scanned (1 hour ago)
Scores higher than 68% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jeonghun917/readfirst). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 382 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.15.0 → 0.15.1 functional
- 4 Nov 26 +12
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.13.0 → 0.15.0 functional
- Package version: 0.13.0 → 0.14.0 functional
- 3 Nov 26 +17
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Schema quality: 64 → 76 ▼ functional
- Dependency health: unverified → pass ▲ functional
- Security disclosure: fail → pass ▲ functional
- Package version: 0.10.0 → 0.13.0 functional
- Package version: 0.10.0 → 0.12.0 functional
- Package version: 0.10.0 → 0.11.0 functional
- 2 Nov 26 −26
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.7.0 → 0.10.0 functional
- Package version: 0.7.0 → 0.9.0 functional
- 1 Nov 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/readfirst@0.15.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jeonghun917/readfirst |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jeonghun917/readfirst/.github/workflows/release.yml@refs/tags/v0.15.1 |
| Rekor log index | 3692692101 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6075b65ca40281c562530ad16fab644d769151449cebaf6c2fb71695aa9afcd61cccbf88f2063be2f296863393700ec5299d21cddd01c027e4ac9c3c8 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_repo ~76
The whole repository against .readfirst/map.json, as a report: rules and risks whose files changed a lot since they were written, hot spots that moved, groups never filled in, code no test reaches through imports, and what readfirst could not see. Use it before larger work, or to decide what to add to the map.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
changed_read_list ~55
The same read list for every file changed on this branch since the base (default origin/main, else main). Call it before finishing, then run the checks it lists.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | git ref to compare against |
No output schema declared.
No examples provided.
check_map ~32
Whether .readfirst/map.json still covers the code: files in no group, patterns that match nothing, broken rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_existing ~96
Before writing a new function, helper or module: the functions, classes, files and map entries that may already do it, matched by words (not meaning) against names and paths. Give a few words about what it does, e.g. "payment retry" or "csv export". If one fits, use or extend it instead of writing another.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | a few words about what you are about to write |
No output schema declared.
No examples provided.
read_list ~62
What to read and check before changing these files: the project rules and risks that apply, the checks to run, the tests that reach the code and the files that use it. Call it before editing.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | paths relative to the repository root |
No output schema declared.
No examples provided.
How do I install the io.github.jeonghun917/readfirst MCP server?
io.github.jeonghun917/readfirst runs locally as an npm package, launched with npx -y readfirst. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · readfirst
claude mcp add jeonghun917-readfirst -- npx -y readfirst
What is the io.github.jeonghun917/readfirst MCP server?
io.github.jeonghun917/readfirst is an MCP server listed in the public MCP registry as io.github.jeonghun917/readfirst. What to read and check before changing a file: project rules, risks, checks and tests per file. This page covers its npm package (readfirst).
Is the io.github.jeonghun917/readfirst MCP server safe to use?
io.github.jeonghun917/readfirst scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jeonghun917/readfirst MCP server expose?
io.github.jeonghun917/readfirst exposes 5 tools: read_list, changed_read_list, find_existing, check_map, audit_repo. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.
Is the io.github.jeonghun917/readfirst MCP server still maintained?
io.github.jeonghun917/readfirst is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.jeonghun917/readfirst MCP server under?
io.github.jeonghun917/readfirst declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.