2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Yats Toolkit
fvinciarelli · MCP server
YATS indexes the repositories you point it at into a knowledge graph and answers questions about them through 20 tools. Your agent can search code by meaning, find symbols, references, callers, callees, implementations and inheritors, list routes, configuration and tests, and ask for a repository or architecture summary. A setup wizard starts the Docker services and asks for an embedding provider: Ollama, OpenAI, Mistral or Voyage. It suits developers who want their agent to navigate their own code.
Written by ooruby from the README of yats-toolkit 0.7.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can look up symbols and call chains in an index of your code instead of reading file after file.
What you could do with it
- Ask your agent to find every implementation of an interface across the repositories you have indexed.
- Follow a function through its callers and callees to map a call chain before you change it.
- Search your code by meaning, for example JWT token validation, and get symbols, files and snippets back.
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
- Command execution is bounded
- inventory
- node child_process (src/benchmark.js:11)
- synchronous shell execution (src/benchmark.js:217)
- synchronous shell execution (src/benchmark.js:662)
- synchronous shell execution (src/benchmark.js:671)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- 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
YATS — Yet Another Token Saver. One-command MCP server that indexes your codebase into a knowledge graph so AI agents (Claude, Cursor, Copilot) can search and navigate it without burning tokens.
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.7.0, the file with digest sha512-A9hoF64x2TdjqiVkK/1n56Li1w9iN0Lbim2gQjkw2YrzijxTmq+kS44hopod0cuVCgadTlX0M/Rotd2g7eFw1Q==, 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
Paste this into your client's MCP configuration.
{
"mcpServers": {
"yats": {
"command": "npx",
"args": [
"-y",
"-p",
"yats-toolkit@0.7.0",
"yats"
]
}
}
}Or run it directly.
npx -y -p yats-toolkit@0.7.0 yatsPinned to 0.7.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- yats-toolkit
- Version read
- 0.7.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/fvinciarelli/yats.ai
- Commit
- 23b491fb1197
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
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/yats-toolkit)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
Similar MCP servers
All MCP serversVerification 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.