CyberMCP is a Model Context Protocol (MCP) server designed for testing backend APIs for security vulnerabilities. It provides a set of specialized tools and resources that can be used by LLMs to identify common security issues in APIs.
MCPpedia last refreshed this data
CyberMCP is an MCP server that CyberMCP is a Model Context Protocol (MCP) server designed for testing backend APIs for security vulnerabilities. It provides a set of specialized tools and resources that can be used by LLMs to identify common security issues in APIs. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 77/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"cybermcp": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AI-powered Cybersecurity API Testing with Model Context Protocol (MCP)
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
security_checklistSecurity testing checklist and best practices
cybermcp://resources/security-checklist
testing_guidesComprehensive security testing guides
cybermcp://resources/testing-guides
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
BridgeGuard MCP Server - Cross-chain bridge security audit tools for AI coding agents. Scan bri...
Regression testing for MCP servers. Checks capabilities, invokes tools, detects schema drift.
MCP Security Weekly
Get CVE alerts and security updates for CyberMCP and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
AI-powered Cybersecurity API Testing with Model Context Protocol (MCP)
CyberMCP is a Model Context Protocol (MCP) server that enables AI agents to perform comprehensive security testing on backend APIs. It provides 14 specialized security tools and 10 resources for identifying vulnerabilities like authentication bypass, injection attacks, data leakage, and security misconfigurations.
# Clone and setup
git clone https://github.com/your-username/CyberMCP.git
cd CyberMCP
npm install
npm run build
# Test the server
npm run test-server
# Start interactive testing
npm run test-interactive
| Category | Tools |
|---|---|
| Authentication | basic_auth, token_auth, oauth2_auth, api_login, auth_status, clear_auth, jwt_vulnerability_check, auth_bypass_check |
| Injection Testing | sql_injection_check, xss_check |
| Data Protection | sensitive_data_check, path_traversal_check |
| Infrastructure | rate_limit_check, security_headers_check |
CyberMCP works with all major AI-powered IDEs:
📖 Complete Setup Guide - Detailed configuration for each IDE
"Use basic_auth with username 'admin' and password 'secret123'
then use auth_bypass_check on https://api.example.com/users
to test for authentication bypass vulnerabilities"
The AI agent will:
# Comprehensive tool testing
npm run test-tools
# Manual interactive testing
npm run test-interactive
# Quick setup verification
npm run quick-start
# MCP Inspector (GUI)
npm run inspector
CyberMCP/
├── src/ # TypeScript source code
│ ├── tools/ # 14 security testing tools
│ ├── resources/ # Security checklists & guides
│ └── utils/ # Authentication & utilities
├── docs/ # Documentation
├── scripts/ # Testing & utility scripts
├── examples/ # Configuration examples
├── dist/ # Built JavaScript (generated)
└── README.md # This file
# Development mode with hot reload
npm run dev
# Build TypeScript
npm run build
# Start server (stdio mode)
npm start
# Start HTTP server
TRANSPORT=http PORT=3000 npm start
git checkout -b feature/new-security-toolThis project is licensed unde