CodeVulnerability

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

OWASP threat scanner auditing codebases for safety leaks.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that scans codebases for security weaknesses against OWASP threat patterns, with a paid premium settlement option.

What you can do
Audit a codebase for safety leaks and security weaknesses using OWASP threat scanning patterns, as described in the registry entry. The manifest lists no individual tools, so the exact operations are not documented. A premium settlement path exists that requires a payment signature header.
When to use it
When you want an assistant to check code for OWASP-style security issues and are willing to connect to a third-party hosted scanner, potentially paying for premium results.
Requirements
A remote MCP connection over SSE to the provider's hosted endpoint; no local runtime or package is needed. No authentication is declared, but premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The server is hosted by a third party, so any code sent to it leaves your machine. Premium settlement involves a payment signature tied to a blockchain-style authorization; treat that signature as sensitive and expect possible charges. No tools or documentation are published, so behavior cannot be verified in advance.

Installation

In SourceWeft

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

Web executable via SSE. 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/io.github.Evozim%2Fcodevulnerability/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "codevulnerability": {
      "type": "sse",
      "url": "https://codevulnerability-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.