Port Scanner Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Scan local or remote hosts for open TCP ports. Runs locally.

The publisher's own server: Port

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant scan local or remote hosts for open TCP ports.

What you can do
  • Scan hosts for open TCP ports, either on the local machine or on remote targets.
  • Report which TCP ports are open on a given host.
  • Runs as a local process on the user's machine, so scans originate from their own network.
When to use it
Useful when you want an assistant to check which TCP ports are reachable on a host, for example during basic network troubleshooting or a quick inventory of services on your own machines.
Requirements
A local runtime with Node.js, since it is distributed as the npm package port-scanner-mcp over stdio. No authentication, environment variables or headers are declared. Desktop-only; it does not run in a web client.
Before you install
Port scanning can be intrusive or unlawful against hosts you do not own or have permission to test; only scan systems you are authorized to check. Scans send traffic to the target hosts, so results and target addresses may be visible to those hosts and to the network in between.

Installation

In SourceWeft

  1. Open Port Scanner Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Port integrations

Port

io.portOfficial publisher

Port's remote MCP server connects Port.io to an IDE, LLM or agent platform, letting an assistant work with your Port.io environment through OAuth-authenticated,

Streamable HTTPWeb executableAuth
Developer ToolsCredential requiredOct 24, 2026

GravityPort

Published by GitHub account fengseekling-coder

MCP server bundled with the GravityPort desktop app that lets Claude, Codex and other clients search and record a local library of AI-generated images, videos…

STDIODesktop only
Files & StorageNot validated yetNov 7, 2026

Worktrack Port

Published by GitHub account CloudCorpRecords

Jira issues and Confluence pages via the REST APIs, as MCP tools.

STDIODesktop only
Communication & CollaborationNot validated yetNov 3, 2026

Videohub Port

Published by GitHub account CloudCorpRecords

YouTube videos, channels, playlists, comments and transcripts as MCP tools.

STDIODesktop only
Not validated yetNov 3, 2026

Tasklist Port

Published by GitHub account CloudCorpRecords

Tasklist Port's local MCP server; no sign-in required; STDIO.

STDIODesktop only
Not validated yetNov 3, 2026