MCP 安全扫描工具

Created By
sxhxlianga year ago
MCP-security-scan: Security scanner for Model Context Protocol servers and tools
Overview

What is MCP Security Scan?

MCP Security Scan is a security scanner designed for detecting and validating the security of Model Context Protocol (MCP) configuration files, including servers, prompts, resources, and tools.

How to use MCP Security Scan?

To use MCP Security Scan, install it using Cargo and run the command with the path to your configuration file. You can also specify advanced options for storage paths and API URLs.

Key features of MCP Security Scan?

  • Scans server configurations in MCP files
  • Automatically validates the security of entities in servers
  • Supports review mode for translating descriptions into Chinese
  • Compatible with various MCP server types (SSE/Stdio)
  • Real-time display of scan progress and results
  • Whitelist management functionality
  • Records scan history and detects configuration changes

Use cases of MCP Security Scan?

  1. Ensuring the security of MCP server configurations
  2. Validating prompts and resources for vulnerabilities
  3. Monitoring changes in configuration over time

FAQ from MCP Security Scan?

  • What programming language is MCP Security Scan written in?

MCP Security Scan is developed in Rust.

  • How do I install MCP Security Scan?

You can install it using the command: cargo install --path .

  • Can I contribute to the project?

Yes! Contributions are welcome through Pull Requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sxhxliang
Star
0
Language
Rust
License
-
Category
security
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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