Opzyai Security Check

com.opzyaiPublished by opzyai.comv0.1.2Updated Oct 24, 2026

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

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local-first security check MCP server that lets an AI coding agent scan for secrets, exposed .env files, git-history leaks and CVEs.

What you can do
Runs security checks on a codebase from the assistant: secret detection, .env exposure, git-history leak scanning and CVE checks. It is described as local-first, so the checks run on the user's own machine. No individual tools are listed in the manifest, so the exact commands and outputs are not documented here.
When to use it
Worth adding when you want an AI coding agent to check a repository for committed secrets, exposed environment files, leaks in git history or known vulnerable dependencies before committing or sharing code.
Requirements
Runs as a local stdio process installed from the npm package @opzyai/mcp, so it needs Node.js and a local project to scan. No authentication, environment variables or headers are declared.
Before you install
It inspects source code and git history, which may include secrets and sensitive files; review what it reads and where any findings or reports are stored before running it on private repositories. No tools, permissions or data handling are documented, so verify behavior yourself.

Installation

In SourceWeft

  1. Open Opzyai Security Check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations