Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.eltociear/skill-audit-mcp

OCI · GHCR.IO/ELTOCIEAR/SKILL-AUDIT-MCP · 2 COMPONENTS

MCP server: static security scanner for MCP servers, agent skills & plugins. 17 attack patterns.

+3 this week 50 Trust /100

Last scanned (1 hour ago)

Scores higher than 74% of OCI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 24 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 181 tokens (~60/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +5
    • Stability: unverified → 0.40 ▲ functional
  • 30 Sept 26 39

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Oct 2026 · Analysed oci/ghcr.io/eltociear/skill-audit-mcp@mcp-1.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 3 exposed · ~181 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit ~73

Audit text content for malicious patterns. Paste skill/plugin content to get a risk score and detailed findings. Detects: download-and-execute, credential exfiltration, key generation, prompt injection, privilege escalation, and more.

NameTypeReqDescription
contentstringyesThe text content to audit (skill file, prompt, instruction, etc.)

No output schema declared.

No examples provided.

audit_directory ~70

Scan a directory for skill/markdown files and audit each one. Returns per-file risk scores and an aggregate summary.

NameTypeReqDescription
extensionsstring–Comma-separated file extensions to scan (default: md,txt,yaml,yml,json)
pathstringyesAbsolute path to the directory to scan

No output schema declared.

No examples provided.

audit_file ~38

Audit a local file for malicious patterns. Provide an absolute file path to scan.

NameTypeReqDescription
pathstringyesAbsolute path to the file to audit

No output schema declared.

No examples provided.

Install

How do I install the io.github.eltociear/skill-audit-mcp server?

io.github.eltociear/skill-audit-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/eltociear/skill-audit-mcp:mcp-1.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/eltociear/skill-audit-mcp

# add to Claude Code
claude mcp add eltociear-skill-audit-mcp -- docker run --rm -i ghcr.io/eltociear/skill-audit-mcp:mcp-1.2.0
Common questions

What is the io.github.eltociear/skill-audit-mcp server?

io.github.eltociear/skill-audit-mcp is listed in the public MCP registry as io.github.eltociear/skill-audit-mcp. MCP server: static security scanner for MCP servers, agent skills & plugins. 17 attack patterns. This page covers its container image (ghcr.io/eltociear/skill-audit-mcp).

Is the io.github.eltociear/skill-audit-mcp server safe to use?

io.github.eltociear/skill-audit-mcp scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.eltociear/skill-audit-mcp server expose?

io.github.eltociear/skill-audit-mcp exposes 3 tools: audit, audit_file, audit_directory. Their descriptions and schemas cost roughly 181 tokens of context every time the server is loaded.

Is the io.github.eltociear/skill-audit-mcp server still maintained?

io.github.eltociear/skill-audit-mcp is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.eltociear/skill-audit-mcp server under?

io.github.eltociear/skill-audit-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.