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.

Opzyai Security Check

NPM · @OPZYAI/MCP · SCANNED SEP 21

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

Available components

npm · @opzyai/mcp 90
0 this week 90 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
Schema Quality & AI Usability83
  • 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 Management97
  • Stability observed for 29 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Opzyai Security Check MCP server?

Opzyai Security Check runs locally as an npm package, launched with npx -y @opzyai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @opzyai/mcp

# add to Claude Code
claude mcp add com-opzyai-mcp -- npx -y @opzyai/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-opzyai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@opzyai/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-opzyai-mcp": {
      "command": "npx",
      "args": [
        "-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"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-opzyai-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@opzyai/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-opzyai-mcp -t stdio -c npx -a -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.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/@opzyai/mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
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

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. 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
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
offlineboolean–Skip the OSV dependency check so nothing leaves the machine
pathstring–Project root to scan; defaults to the current working directory

No output schema declared.

No examples provided.

Common questions

What is the Opzyai Security Check MCP server?

Opzyai Security Check is an MCP server listed in the public MCP registry as com.opzyai/mcp. Local-first security check for AI coding agents: secrets, .env exposure, git-history leaks, CVEs. This page covers its npm package (@opzyai/mcp).

Is the Opzyai Security Check MCP server safe to use?

Opzyai Security Check scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Opzyai Security Check MCP server expose?

Opzyai Security Check exposes 1 tool: security_check. Their descriptions and schemas cost roughly 106 tokens of context every time the server is loaded.

Is the Opzyai Security Check MCP server still maintained?

Opzyai Security Check is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Opzyai Security Check MCP server under?

Opzyai Security Check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.