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

Opzyai Security Check

NPM · @OPZYAI/MCP · SCANNED AUG 3

Local-first security check for AI coding agents: secrets, .env exposure, git-history leaks, CVEs.

Available components

+35 this week 75 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency71
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 106 tokens (~106/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @opzyai/mcp

# add to Claude Code
claude mcp add com-opzyai-mcp -- npx -y @opzyai/mcp
# add to Codex CLI
codex mcp add com-opzyai-mcp -- npx -y @opzyai/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-opzyai-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@opzyai/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-opzyai-mcp --command npx --arg -y --arg @opzyai/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-opzyai-mcp:
    command: "npx"
    args: ["-y", "@opzyai/mcp"]
// mcp.json
{
  "mcpServers": {
    "com-opzyai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@opzyai/mcp"
      ]
    }
  }
}
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.

  • 3 Aug 26 +1

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

  • 2 Aug 26 +56
    • Provenance: pass → unverified security
    • Install scripts: pass → unverified security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: thfothijn/opzyai-mcp security
    • Maintenance: pass → unverified functional
    • License: pass → unverified functional
    • Security disclosure: fail → unverified functional
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.23 functional
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 1 Aug 26 −41
    • Known CVEs: partial → unverified security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Dependency health: partial → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 −9
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 28 Jul 26 +46
    • Known CVEs: unverified → partial security
    • Provenance: unverified → pass security
    • Install scripts: unverified → pass security
    • The attested source repository moved: thfothijn/opzyai-mcp security
    • Security disclosure: unverified → fail functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • Licence: MIT functional
  • 27 Jul 26 40

    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 3 Aug 2026 · Analysed npm/@opzyai/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
thfothijn/opzyai-mcp
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/thfothijn/opzyai-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index:
2058670792
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:7bcd4d47b95dab1159eee3b5d076d2863c405cb1527db064e162a75d51b3f4ad5efed519336ce33e5dc4c76746f0206f4ef3f4b6e8d2193132440187e
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 1 exposed · ~106 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.

Tool Tokens
security_check ~106

Run a local security check on the project in this workspace: finds hardcoded API keys, committed/exposed .env files, secrets in git history, and known-vulnerable dependencies. Runs entirely on this machine. Use when asked to do a security check, audit, or "is this safe to ship".

NameTypeReqDescription
offlinebooleanSkip the OSV dependency check so nothing leaves the machine
pathstringProject root to scan; defaults to the current working directory

No output schema declared.

No examples provided.