MCP Server logo

MCP Server

by middleBrick

Scans API endpoints for OWASP Top 10, LLM, and GraphQL security vulnerabilities through MCP tools.

Install MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-141": {
      "command": "npx",
      "args": [
        "-y",
        "@middlebrick/mcp-server"
      ],
      "env": {
        "MIDDLEBRICK_API_KEY": "YOUR_VALUE_HERE",
        "MIDDLEBRICK_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 3 tools correctly (1d ago).

Overview

The middleBrick/mcp-server MCP server connects MCP-compatible assistants to middleBrick API security scanning. It exposes tools to start an API scan, retrieve a scan by ID, and list earlier scans with pagination and status filters. Configure it as an npx-launched server with a middleBrick API key, then use it from Claude Desktop or Cursor. Reach for it when an assistant needs to initiate or inspect API security scans through tool calls.

Use cases

  • Scan an API endpoint for security vulnerabilities
  • Retrieve results for a previous scan
  • List scans by status
  • Review scans with pagination

Key features

  • API endpoint vulnerability scanning
  • OWASP Top 10 coverage
  • LLM security scanning
  • GraphQL security scanning
  • Scan retrieval by ID
  • Status-filtered scan listing

Tools3

What MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~195 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

10/10 checks healthy over the last 56d

What it can do

From the 3 tools this server returned when we ran it.

Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age235 days
Maintainers1

Observed 2026-11-07 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @middlebrick/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads114Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.

How MCP Server works

What middleBrick/mcp-server does

The middleBrick/mcp-server MCP server gives AI assistants access to middleBrick API security scanning. Its tools cover the basic scan lifecycle: submit an API endpoint for analysis, retrieve the results of a known scan, and browse previously created scans.

The repository describes scanning for OWASP Top 10, LLM, and GraphQL security vulnerabilities. The scan request accepts an endpoint URL and can optionally specify an HTTP method. If no method is supplied, the request uses GET.

How it works

An assistant invokes scan_api with the target URL and, optionally, an HTTP method. The tool returns a scan that can later be looked up with get_scan, using the scan ID returned by the earlier operation.

list_scans supports basic result management. Callers can provide a maximum result count, an offset for skipping records, and a status filter. Supported status values are queued, processing, completed, and failed. This makes it possible to check pending work or find completed and unsuccessful scans without manually tracking every scan record.

The server is intended to run as an MCP process launched with npx. The examples configure it for Claude Desktop and Cursor, where the assistant can call the tools through the client’s MCP integration.

Setup and configuration

Create an API key through the middleBrick dashboard and provide it as MIDDLEBRICK_API_KEY. Both the Claude Desktop and Cursor examples launch the package with npx -y @middlebrick/mcp-server and pass the key through the server’s environment configuration.

For Claude Desktop, add a middlebrick entry to claude_desktop_config.json. For Cursor, add the equivalent server entry to .cursor/mcp.json. The command and environment configuration are the same in both examples; only the client configuration file differs.

MIDDLEBRICK_BASE_URL is optional and allows the API URL to be overridden. The documented required setting is MIDDLEBRICK_API_KEY; without it, the server does not have the credential shown in the setup configuration.

Tools and capabilities

  • scan_api: starts a vulnerability scan for a required API endpoint URL. Accepts an optional HTTP method, defaulting to GET.
  • get_scan: retrieves the results associated with a required scan ID.
  • list_scans: lists prior scans, with optional limit, offset, and status filtering.

The middleBrick/mcp-server MCP server therefore fits workflows that need an assistant to start API security checks and follow their progress or results. It does not document tools for editing APIs, remediating findings, or running scans without the middleBrick service.

Limitations and notes

The provided interface documents endpoint URL and HTTP method inputs, but does not describe authentication options for the target API, request headers, request bodies, or configuration for individual vulnerability categories. It also does not specify whether scans complete synchronously; the presence of queued and processing statuses indicates that callers should be prepared to retrieve results separately.

The README provides setup examples for Claude Desktop and Cursor only. License information identifies the project as Apache 2.0 under middleBrick.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server

middleBrick/mcp-server is an MCP server that connects AI assistants to middleBrick API security scanning. Its main tools scan API endpoints for vulnerabilities, retrieve results for earlier scans, and list scans with optional pagination and status filtering. It runs with an API key and supports Claude Desktop and Cursor configurations.

Install it through an MCP client configuration that runs `npx -y @middlebrick/mcp-server`. Add the command to Claude Desktop or Cursor, set `MIDDLEBRICK_API_KEY`, and obtain the key from the middleBrick dashboard.

Yes, middleBrick/mcp-server works with Cursor through `.cursor/mcp.json`. Add a `middlebrick` MCP server entry using the documented npx command and provide `MIDDLEBRICK_API_KEY` in its environment settings.

It scans APIs for OWASP Top 10, LLM, and GraphQL security vulnerabilities.

Call `get_scan` with the scan ID to retrieve results from an earlier scan. Use `list_scans` when you need to find scans, filter them by queued, processing, completed, or failed status, or paginate through the results.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-server-141?style=directory)](https://allmcps.com/mcp/mcp-server-141)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-server-141"><img src="https://allmcps.com/api/badge/mcp-server-141?style=directory" alt="MCP Server on AllMCPs" /></a>