CyberMCP - Cybersecurity API Testing with MCP

Created By
ricautsa year ago
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.
Overview

what is CyberMCP?

CyberMCP is a Model Context Protocol (MCP) server designed for testing backend APIs for security vulnerabilities. It provides specialized tools and resources for identifying common security issues in APIs.

how to use CyberMCP?

To use CyberMCP, clone the repository, install dependencies, and run the server using either stdio or HTTP transport. Connect to the server with any MCP client that supports the Model Context Protocol.

key features of CyberMCP?

  • Authentication Vulnerability Testing: Check for JWT vulnerabilities and weak authentication mechanisms.
  • Injection Testing: Test for SQL injection and XSS vulnerabilities.
  • Data Leakage Testing: Identify sensitive data exposure issues.
  • Rate Limiting Testing: Test for rate limiting bypass and DDoS vulnerabilities.
  • Security Headers Testing: Check for missing or misconfigured security headers.
  • Comprehensive Resources: Access checklists and guides for API security testing.

use cases of CyberMCP?

  1. Testing APIs for security vulnerabilities before deployment.
  2. Ensuring compliance with security standards.
  3. Conducting security audits for existing APIs.

FAQ from CyberMCP?

  • Can CyberMCP test all types of APIs?

Yes! CyberMCP is designed to test various types of APIs for security vulnerabilities.

  • Is CyberMCP free to use?

Yes! CyberMCP is open-source and free to use.

  • What programming language is CyberMCP written in?

CyberMCP is written in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ricauts
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago