MCP.so
ログイン
F

Fscan_mcp

@steveopen1

Fscan_mcp について

概要はまだありません

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

steveopen1

投稿者

steveopen1

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Fscan_mcp?

Fscan_mcp is a port scanning and vulnerability detection MCP service wrapper based on the fscan tool. It provides standardized interfaces via the FastMCP framework for integration into other systems, targeting security researchers and developers.

How to use Fscan_mcp?

Ensure Python 3.12+ and the fscan.exe binary are present. Install dependencies with pip install -r requirements.txt, then start the service using uv --directory /path/to/fscan_mcp --with mcp mcp run fscan_mcp_server.py. Invoke via MCP protocol with the required ip parameter; optional parameters include port_range, proxy, output_path, input_file, report, and vuln_scan.

Key features of Fscan_mcp

  • Wraps fscan for port scanning and vulnerability detection
  • Exposes scanning parameters via MCP protocol
  • Supports custom port ranges and proxy settings
  • Generates scan reports (optional)
  • Configurable via config.py and logger.py modules

Use cases of Fscan_mcp

  • Automating port scans across multiple target IPs
  • Integrating vulnerability scanning into CI/CD pipelines
  • Generating structured reports from fscan output
  • Scanning internal networks with proxy support

FAQ from Fscan_mcp

What are the runtime dependencies?

Python 3.12+ is required, along with the fscan.exe binary placed in the project root directory. Dependencies are installed via pip install -r requirements.txt.

How are scan results returned?

Results are output via stdout; optional report files are saved to a specified path.

Is authentication or authorization supported?

The README does not mention any authentication or authorization mechanisms for the MCP interface.

What transports does Fscan_mcp use?

The service uses the MCP protocol; specific transport details (e.g., STDIO or HTTP) are not specified in the README.

Are there any restrictions on scanning?

The README notes that users should confirm the target system allows port scanning before proceeding.

コメント

「その他」の他のコンテンツ