This will not tell you whether your README explains the project. It will tell you, consistently and across a whole directory of them, whether the header renders well, whether the badges are where readers look, and whether the two language versions match — the things that are obvious in one repository and invisible across thirty. Read it as a house-style checker for a set of projects rather than as documentation review, and note the checklist is opinionated: centred headers, SVG banners, English and Japanese badges.
An MCP server that evaluates README files in a project directory against a presentation checklist: whether there is a header image and how good it is, whether the title and badges are centred, and whether English and Japanese documentation badges are present and correctly formatted. It returns a score with the individual findings behind it.
- Every README in a project directory evaluated from one call, with the path to each — `evaluate_readme`
- A structured result rather than prose: whether a header image exists, its quality broken into gradient, animation, rounded corners, English text and project-specificity, whether the header image, title and badges are centred, whether English and Japanese badges exist and use the right format, a numeric score, and a list of suggestions
- SVG header analysis that reads the file, so "is this image actually about this project" is answered from its contents rather than from its filename
Nothing external — no account, no key, no network; it reads files from a path you give it. Node.js 18+ and npm or yarn. There is no published package: clone, `npm install`, `npm run build`, and point your client at `build/index.js`. Header images need to be SVG files in the project's `assets/` directory with valid XML for the analysis to find them, and badges are recognised in shields.io format.