Security Operations Multi-Tool Platform (MCP)

Created By
securityfortecha year ago
All-in-one security testing toolbox that brings together popular open source tools through a single MCP interface. Connected to an AI agent, it enables tasks like pentesting, bug bounty hunting, threat hunting, and more.
Overview

What is secops-mcp?

secops-mcp is an all-in-one security testing toolbox that integrates popular open-source tools through a single MCP interface, connected to an AI agent for enhanced security tasks.

How to use secops-mcp?

To use secops-mcp, clone the repository, build the Docker image, and integrate it with Claude Desktop for seamless operation.

Key features of secops-mcp?

  • Integration of multiple security tools in one interface
  • AI agent assistance for security tasks
  • Support for various security testing methodologies including pentesting and bug bounty hunting

Use cases of secops-mcp?

  1. Conducting penetration tests on web applications
  2. Performing vulnerability assessments using integrated tools
  3. Engaging in bug bounty hunting with automated tools

FAQ from secops-mcp?

  • Is secops-mcp suitable for beginners?

Yes, secops-mcp is designed to be user-friendly and integrates various tools to simplify security testing.

  • What tools are included in secops-mcp?

It includes tools like Nuclei, SQLMap, Nmap, and many others for comprehensive security testing.

  • Is secops-mcp free to use?

Yes, secops-mcp is open-source and free to use under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
securityfortech
Star
96
Language
Python
License
MIT license
Category
security
Tags

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