Opzyai Security Check MCP server

by opzyai.com·com.opzyai/mcp·v0.1.2

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

B83/100grade B

What users say

No reviews yet

Safety scan

B83/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Opzyai Security Check yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

security_checkwrite action
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".

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings

Code scan2 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identitynamespace and repository owner differ; GitHub account older than a year5/10

Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 83/100; higher than 65% of 1,119 Developer tools servers
Tools: 1; the typical Developer tools server has 7
Tools that change things: 100%; typical: 5%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 change

Runs npx -y @opzyai/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y @opzyai/mcp

Is Opzyai Security Check MCP server safe?: Mostly: it is graded B (83/100). Read the Opzyai Security Check safety report
How do I install Opzyai Security Check?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Opzyai Security Check need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Opzyai Security Check maintained?: The last commit was 124 days ago (2026-07-03). The latest release is v0.1.2.
What can I use instead of Opzyai Security Check?: Servers from other publishers that do the same job: Repowise MCP server, argot MCP server and Nexusmem MCP server.
How does Opzyai Security Check compare with other Developer tools MCP servers?: safety score 83/100 (higher than 65% of 1,119 Developer tools servers); tools 1 (the typical Developer tools server has 7); tools that change things 100% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Same job from other publishers: the closest match first, then the best rated.

Repowise
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
not reviewed
Established
B
argot
Read-only context and complete checks against patterns learned from git history. Local; no LLM.
not reviewed
Established
B
Nexusmem
Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.
not reviewed
Growing
A
Agent Memory
Git-native project memory for AI coding agents: Markdown source of truth, reviewable, secret-safe.
not reviewed
Growing
A
SoloMD
Read and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.
not reviewed
Established
B