Lets your agent ask a NEAT code graph about dependencies, blast radius and root causes of failures.
Claude Skill
neat.is · MCP server
Plugs NEAT's twenty-four MCP tools into Claude Code. The package ships no compiled code: it carries the MCP server entry for Claude Code, a search-nudge hook that steers the agent toward NEAT's graph before it scans a repository with search, and graph-first guidance you can paste into project instructions for any agent. The NEAT command line can merge the entry and install the hook and guidance.
Written by ooruby from the README of @neat.is/claude-skill 0.10.5.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent is pointed at NEAT's graph before it scans a repository, with NEAT's tools already wired into Claude Code.
What you could do with it
- Use the NEAT command line to add its MCP tools to Claude Code without editing settings by hand.
- Install the search-nudge hook so Claude Code is steered to NEAT's graph before it scans a repository.
- Paste the graph-first guidance into your project instructions so any agent consults the graph before searching files.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Licence and provenance
- finding
- no LICENCE file at the root (.)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Claude Code skill drop-in for NEAT — wires the @neat.is/mcp server into Claude's MCP config
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.10.5, the file with digest sha512-ACkv1Ov6d7FWDHvTbJ3HSvjynjLwC8O3lMIbHyXKo6B8ez8a7daaddWx/Z3i4QcsoZFAW3Bf3qYqAWNT98hOGw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
This one installs no executable, so there is nothing to run. It is a library you import into your own process. Add it with npm i @neat.is/claude-skill@0.10.5 and call it from your code.
Where this came from
- Registry
- npm
- Package
- @neat.is/claude-skill
- Version read
- 0.10.5
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/neat-is-claude-skill)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from neat.is
See the storefrontSimilar MCP servers
All MCP serversAdds Storybook component and story documentation tools to an MCP server you run yourself.
Lets your agent control and inspect a live Chrome browser using Chrome DevTools.
Pulls version-specific library docs and code examples straight into your agent's context.
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.