Opzyai Pro
com.opzyaiPublished by opzyai.comOfficial publisherv1.0.0Updated Oct 24, 2026
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
Overview
Remote MCP server that lets an assistant run deep security scans of repositories you own: dependency CVEs, SAST findings and secrets in git history.
- What you can do
- Run deep security scans against repositories you own from the editor.
- Check dependencies for known CVEs.
- Perform static application security testing (SAST) on the code.
- Detect secrets exposed in git history.
- No individual tools are documented, so the exact operations are not listed.
- When to use it
- Useful when you want an assistant to audit your own repositories for vulnerable dependencies, code-level security issues or leaked credentials before shipping, without leaving the editor.
- Requirements
- A remote MCP endpoint at opzyai.com over streamable HTTP. A bearer personal access token is required in the Authorization header, minted in the provider's settings under MCP access tokens, with the 'Bearer ' prefix. No local package or environment variables are needed.
Installation
In SourceWeft
- Open Opzyai Pro in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.opzyai%2Fpro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"opzyai-pro": {
"type": "http",
"url": "https://www.opzyai.com/api/mcp/pro/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
39% 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.