Clean scanStatic scanned
Gives your agent a static, offline first look at a suspicious file: hashes, type, entropy and strings.
16.4k installs/moMIT
Yotta Verify MCP
yottameta · MCP server
Yotta Verify MCP, also called YuanXin MCP, is a stdio MCP server that scans agent skills, plugins and MCP servers before you install them. A deterministic static scan checks for prompt injection, malicious patterns, skill file integrity and permissions. Its four tools scan a skill folder, archive or package for a verdict with severity counts and findings, generate a badge, run a CI gate against a severity limit and produce a report in Markdown or JSON. It suits developers who want to check a skill before adding it to an agent.
Written by ooruby from the README of @yottameta/yotta-verify-mcp 0.4.5.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You can check what is inside a skill or plugin with a fixed set of rules before it reaches your agent.
What you could do with it
- Scan a skill folder before installing it and read the verdict, severity counts and findings.
- Add a CI gate that fails when the worst finding is above the severity limit you set.
- Write a verification report for a skill in Markdown or JSON and save it to a path you choose.
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 (test/version-consistency.test.js:6)
- synchronous shell execution (test/version-consistency.test.js:18)
- node child_process (scripts/threat_engine.py:25)
- node child_process (scripts/threat_engine.py:26)
- 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.
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
YuanXinMCP (元信MCP) - the pre-install security scanner for Agent skills, exposed as a stdio MCP server: scan_skill (dir/package -> verdict + findings), generate_badge (audited badge), gate_check (CI gate), get_report (JSON/Markdown). Local offline static s
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.4.5, the file with digest sha512-CgvQ0RHzmWCC7IZOQv/aG8hozPeYpaZxuiksg3AlibknC18pOYlvEBCyyfxJsK4CWzxBtPF0LT7vmUy0O7f2tw==, 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": {
"yotta-verify-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"@yottameta/yotta-verify-mcp@0.4.5",
"yotta-verify-mcp"
]
}
}
}Or run it directly.
npx -y -p @yottameta/yotta-verify-mcp@0.4.5 yotta-verify-mcpPinned to 0.4.5, 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
- @yottameta/yotta-verify-mcp
- Version read
- 0.4.5
- 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/yottameta/yotta-verify-mcp
- Commit
- 4dda196360c1
- 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/yottameta-yotta-verify-mcp)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
More from yottameta
See the storefrontSimilar MCP servers
All MCP servers2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Clean scanStatic scanned
Lets your agent control and inspect a live Chrome browser using Chrome DevTools.
9.9M installs/moApache-2.0
Clean scanStatic scanned
Pulls version-specific library docs and code examples straight into your agent's context.
3.9M installs/moMIT
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.