Fscan_mcp

Created By
steveopen1a year ago
Overview

what is fscan_mcp?

fscan_mcp is a service wrapper for port scanning and vulnerability detection based on the fscan tool, providing standardized interfaces for integration into other systems through the FastMCP framework.

how to use fscan_mcp?

To use fscan_mcp, initialize the environment by ensuring Python 3.12+ is installed, install dependencies, start the service, and then call the service using the MCP protocol with the required parameters.

key features of fscan_mcp?

  • Port scanning and vulnerability detection capabilities
  • Standardized MCP interface for easy integration
  • Configurable scanning parameters and output options

use cases of fscan_mcp?

  1. Conducting security assessments on networked systems
  2. Automating vulnerability scanning in CI/CD pipelines
  3. Integrating with other security tools for comprehensive analysis

FAQ from fscan_mcp?

  • What is required to run fscan_mcp?

You need Python 3.12+ and the fscan executable in the project root.

  • Can fscan_mcp scan any IP address?

Yes, but ensure that the target system allows port scanning before proceeding.

  • How are the results returned?

Scan results are returned via stdout, and reports can be saved to specified paths.

Project Info
Created At
a year ago
Updated At
9 months ago
Author Name
steveopen1
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)

a day ago