# Mcp Server Security Scanner (`flowsentry/mcp-server-security-scanner`) Actor

- **URL**: https://apify.com/flowsentry/mcp-server-security-scanner.md
- **Developed by:** [Mihai Sijarvis](https://apify.com/flowsentry) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## MCP Server Security Scanner (n8n + MCP configs)

Security scanner for **n8n workflow exports** and **MCP server configurations**, built from the open-source [FlowSentry](https://github.com/vasilicasijarvis/flowsentry) engine. 18 rules mapped to the OWASP Agentic Top 10.

### What it detects

- Webhooks without authentication (critical)
- Hardcoded secrets in node parameters and HTTP headers (critical)
- Command injection via Execute Command nodes (critical)
- Overly permissive CORS / file access
- Prompt-injection-prone LLM nodes with untrusted input
- And 13 more rules - see the full list in the repository

### How to use

1. **Try it instantly**: leave "Scan built-in vulnerable example" checked and run - you get real findings from a bundled demo workflow.
2. **Scan your own workflow**: paste your n8n workflow export JSON into "Workflow JSON" and run.
3. Check the output dataset for findings with rule id, severity, affected node, message, remediation and evidence.

### Output

The default dataset contains one item:

```json
{
  "files_scanned": 1,
  "summary": { "critical": 2, "high": 1, "medium": 1, "low": 0, "info": 0 },
  "findings": [
    {
      "rule_id": "FS001",
      "severity": "critical",
      "node": "Webhook",
      "message": "Webhook has no authentication",
      "remediation": "Enable basic auth or header auth on the webhook node"
    }
  ]
}
```

### Options

- **Workflow JSON**: your n8n export (the `{ "nodes": [...] }` object or the full export file).
- **Scan built-in vulnerable example**: run against the bundled demo workflow.
- **Fail run at severity**: mark the run FAILED when findings at/above this severity exist (`never` disables). Useful in CI pipelines - schedule the Actor against your workflow repository folder.

### Need deeper scans?

The full engine (18 rules, SARIF 2.1.0 reports, CI mode) is open source at [github.com/vasilicasijarvis/flowsentry](https://github.com/vasilicasijarvis/flowsentry) (`pip install flowsentry`), and there's a free in-browser scanner at [flowsentry.vercel.app](https://flowsentry.vercel.app).

# Actor input Schema

## `workflowJson` (type: `string`):

Paste an n8n workflow export (or MCP server config JSON) to scan. Takes precedence over the built-in example if provided.

## `useExample` (type: `boolean`):

Run the scanner on a bundled demo workflow that triggers several rules. Useful to see the output format instantly.

## `failOnSeverity` (type: `string`):

Sets the Actor run status to FAILED when findings at or above this severity exist (like the CLI --fail-on flag).

## Actor input object example

```json
{
  "useExample": true,
  "failOnSeverity": "high"
}
```

# Actor output Schema

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

One item per scan: files\_scanned, summary by severity, and findings with rule id, severity, node, message, remediation, evidence and OWASP Agentic Top 10 mapping.

# 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 = {
    "workflowJson": "",
    "failOnSeverity": "high"
};

// Run the Actor and wait for it to finish
const run = await client.actor("flowsentry/mcp-server-security-scanner").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 = {
    "workflowJson": "",
    "failOnSeverity": "high",
}

# Run the Actor and wait for it to finish
run = client.actor("flowsentry/mcp-server-security-scanner").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 '{
  "workflowJson": "",
  "failOnSeverity": "high"
}' |
apify call flowsentry/mcp-server-security-scanner --silent --output-dataset

```

## MCP server setup

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

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/mbIYrbOMF8TjMFjO2/builds/kLzizrg1AKuohai6c/openapi.json