Xray Mcp

Created By
kaixin008-tech9 months ago
This is an enhanced MCP (Model Context Protocol) server that provides xray vulnerability scanning capabilities for ModelScope hosting.
Overview

what is Xray MCP?

Xray MCP is an enhanced Model Context Protocol server that provides xray vulnerability scanning capabilities for ModelScope hosting.

how to use Xray MCP?

To use Xray MCP, install Python 3.7+, set up the xray binary, and run the server using the command python server.py. You can then send JSON-RPC requests to perform scans.

key features of Xray MCP?

  • xray_scan: Perform vulnerability scans on target URLs with configurable options.
  • xray_version: Retrieve the version information of the xray scanner.
  • xray_start_proxy: (Planned) Start xray in passive proxy mode for real-time scanning.
  • xray_service_scan: (Planned) Scan services on non-HTTP targets.

use cases of Xray MCP?

  1. Scanning web applications for vulnerabilities.
  2. Integrating with ModelScope for enhanced security.
  3. Real-time vulnerability detection in proxy mode (planned).

FAQ from Xray MCP?

  • Can Xray MCP scan any URL?

Yes, Xray MCP can scan any target URL provided it is accessible.

  • Is Xray MCP free to use?

Yes, Xray MCP is open-source and free to use.

  • What programming language is required?

Xray MCP requires Python 3.7 or higher.

Server Config

{
  "mcpServers": {
    "xray-mcp": {
      "command": "node",
      "args": [
        "path/xray-mcp-server/server.py"
      ],
      "env": {
        "XRAY_PATH": "path/bin/xray",
        "XRAY_OUTPUT_DIR": "path/xray-mcp-server/xray-results",
        "XRAY_CONFIG": "path/xray-mcp-server/config/xray-config.yaml"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
kaixin008-tech
Star
-
Language
-
License
-
Category
security

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)

20 hours ago
Gpt Scrambler

2 days ago