MCP Tools Directory
← Browse integrations

Developer tools

io.github.YottaMeta/yotta-verify-mcp

Free account · sign-in required

Contact io.github.YottaMeta/yotta-verify-mcp

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

Pre-install security scanner for AI agent skills (local stdio MCP). Offline static scan; no upload.

Transport
stdio
Authentication
none
Initial setup
none
Runtime
unattended
Evidence
documented
Version
0.4.2
Package
@yottameta/yotta-verify-mcp
Last compatibility test
Not independently tested

Connect your agent

@yottameta/yotta-verify-mcp

Publisher README and executable npm manifest reviewed at their captured hashes. The package and scanned targets were not installed or executed, and the documentation is not an independent security audit.

Capabilities: Static skill and package scanning, Verification reports, CI severity gates, Audit badge generation

Connected profiles

Additional details

Registry identifier

io.github.YottaMeta/yotta-verify-mcp

Source ↗ · Checked 2026-09-17
Published version

0.4.2

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

@yottameta/yotta-verify-mcp

Source ↗ · Checked 2026-09-20
Source manifest version

0.4.3

Source ↗ · Checked 2026-09-20
Unattended configuration

The publisher documents a standard stdio MCP server that an MCP client launches with the npm command; directory scans are local and offline, and the reviewed package was not executed.

Source ↗ · Checked 2026-09-20
Authentication and prerequisites

No service credential is documented for the local scanner. Directory scans make no network calls; scanning a named npm package may download that public package before performing the local static scan.

Source ↗ · Checked 2026-09-20
Connection configuration

Configure the MCP client to launch `npx -y @yottameta/yotta-verify-mcp` over stdio.

Source ↗ · Checked 2026-09-20
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-20