Mcp Server Security Scanner

io.github.vpatser1Published by GitHub account vpatser1v1.1.4Updated Oct 24, 2026

Scan MCP configs for 30+ CVEs, prompt injection, tool poisoning; validate OAuth configs

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that scans MCP configurations for known CVEs, prompt injection, tool poisoning and OAuth misconfiguration.

What you can do
Scan MCP configuration files for more than 30 known CVEs, prompt injection and tool poisoning issues, and validate OAuth configurations. The manifest lists no individual tools, so the exact commands are not documented here. It runs as a local process on the user's machine over stdio.
When to use it
Useful when you maintain MCP server configurations and want an automated check for known vulnerabilities, injected prompts, poisoned tool definitions or weak OAuth settings before trusting or deploying them.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. A LICENSE_KEY environment variable is required for full use; it is emailed after purchase. Without it, a free trial allows 3 calls per tool.
Before you install
Full functionality is paid: a license key must be purchased, and without it usage is limited to a free trial. The license key is a secret passed via the LICENSE_KEY environment variable and should not be shared or committed. The scanner reads MCP configuration files, which may contain credentials or endpoint details.

Installation

In SourceWeft

  1. Open Mcp Server Security Scanner 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. v1.1.4LatestSep 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.