# MCP Security & Vulnerability Auditor (2026) (`neon_innovation_lab/mcp-security-auditor`) Actor

Zero-execution security scanner for Model Context Protocol (MCP) servers. Audits for Command Injection (CWE-78), Path Traversal (CWE-22), Secret Leaks (CWE-798), and Unauthenticated Transports. Generates verified Trust Scores and remediation reports.

- **URL**: https://apify.com/neon\_innovation\_lab/mcp-security-auditor.md
- **Developed by:** [Neon Innovation Lab](https://apify.com/neon_innovation_lab) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.25 / mcp server audited

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## MCP Security & Vulnerability Auditor (2026)

A zero-execution security auditor and trust scoring engine for **Model Context Protocol (MCP)** servers.

Detect critical remote code execution (RCE), arbitrary file access, credential leaks, and transport security flaws in any MCP repository before connecting it to your AI agents, Claude Desktop, or Cursor environments.

***

### 🛡️ Why Use This Actor?

With thousands of MCP servers published across registries, AI agents have direct access to filesystems, command lines, and internal databases.

Following 30+ CVE disclosures against MCP tools in 2025 and 2026, standard security practices now require continuous verification of third-party tools.

Unlike standard runtime scanners that attempt to run arbitrary `stdio` commands defined in target configs (creating severe RCE hazards for the scanning host), this Actor uses **pure static AST analysis**. It inspects the source code syntax tree and configurations without executing untrusted code.

***

### 🔍 Vulnerability Checks Covered

| Rule ID | Severity | CWE | Description |
| :--- | :--- | :--- | :--- |
| **MCP-SEC-001** | CRITICAL | **CWE-78** | **Command Injection**: Detects `subprocess.run(shell=True)`, `os.system()`, and dynamic string interpolation in shell calls. |
| **MCP-SEC-002** | HIGH | **CWE-22** | **Path Traversal / Arbitrary File Access**: Detects file read/write tools lacking strict root boundary checks (`Path.is_relative_to()` or `commonpath`), as well as ZipSlip/TarSlip archive extractions. |
| **MCP-SEC-003** | CRITICAL | **CWE-798** | **Credential & Secret Exposure**: Scans for leaked OpenAI, Anthropic, GitHub, AWS, and Slack keys, and flags tools returning raw `os.environ`. |
| **MCP-SEC-004** | HIGH | **CWE-306** | **Unauthenticated Remote Transport**: Flags SSE / HTTP endpoints bound to `0.0.0.0` without authentication tokens. |
| **MCP-SEC-005** | HIGH | **CWE-1384** | **Tool Poisoning & Prompt Injection**: Flags adversarial instructions and zero-width homoglyph obfuscation in tool docstrings and descriptions. |

***

### 📥 Input Configuration

```json
{
  "repositoryUrls": [
    "https://github.com/modelcontextprotocol/servers"
  ],
  "subDirectories": [
    "src/everything",
    "src/fetch"
  ],
  "minimumPassScore": 80
}
```

- **`repositoryUrls`** *(Required)*: List of public Git URLs for the MCP server repositories to audit.
- **`subDirectories`** *(Optional)*: List of subdirectories to audit individually (ideal for monorepos).
- **`minimumPassScore`** *(Optional, Default: `80`)*: The minimum Trust Score (0–100) required to consider the repository passed.

***

### 📤 Output

#### 1. Structured Dataset Records

Each audited server produces a structured JSON record containing:

- `trust_score`: Score from `0` to `100`.
- `grade`: Security letter grade (`A+`, `A`, `B`, `C`, `F`).
- `passed`: Boolean indicating if the score meets `minimumPassScore`.
- `findings`: Array of detailed findings with file paths, line numbers, CWE IDs, code snippets, and specific remediation advice.

#### 2. Downloadable Markdown Report

The full human-readable audit report is saved to the run's default Key-Value store under **`OUTPUT_REPORT.md`**.

# Actor input Schema

## `repositoryUrls` (type: `array`):

List of Git repository URLs for the MCP servers you want to audit (e.g. GitHub or GitLab).

## `subDirectories` (type: `array`):

Optional list of subdirectories to audit individually (useful for monorepos like modelcontextprotocol/servers).

## `minimumPassScore` (type: `integer`):

Minimum acceptable trust score (0–100) before marking the audit as failing.

## Actor input object example

```json
{
  "repositoryUrls": [
    "https://github.com/modelcontextprotocol/servers"
  ],
  "minimumPassScore": 80
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "repositoryUrls": [
        "https://github.com/modelcontextprotocol/servers"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neon_innovation_lab/mcp-security-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "repositoryUrls": ["https://github.com/modelcontextprotocol/servers"] }

# Run the Actor and wait for it to finish
run = client.actor("neon_innovation_lab/mcp-security-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "repositoryUrls": [
    "https://github.com/modelcontextprotocol/servers"
  ]
}' |
apify call neon_innovation_lab/mcp-security-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neon_innovation_lab/mcp-security-auditor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/A7eGA1Ln6F9bs8hm4/builds/oADQw6EO8mcx0bueU/openapi.json