Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_port_scan

Probe a live host for open TCP ports using TCP connect scanning. Returns port status (open, closed, filtered) and service detection. Only scan systems you own or have permission to test.

Instructions

TCP Connect Port Scanner. Probe a live host for open TCP ports by opening real outbound TCP connections from this server to each requested port and reporting which answer (open), refuse (closed), or time out (filtered). Use this to detect actually-listening services on a host you control; use network_tcp_udp_port_reference instead for offline lookup of what a port number conventionally means (no live probe). Makes outbound network connections from the server, resolves the host and pins the scan to the first publicly-routable IP (private and reserved ranges are rejected), is a TCP connect scan the target may log, and is heavily rate-limited (1 per minute, 5 per hour, 20 per day anonymous) with CAPTCHA and terms acceptance. Only scan systems you own or have permission to test. Returns per-port status with detected service name and response time, plus open/closed/filtered summary counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesTarget hostname or IP address to scan. Must resolve to a publicly-routable address (private and reserved IPs are rejected).
portsNoComma-separated ports and ranges (for example 80,443,8080 or 1-1024). Each port must be 1-65535; at most 100 distinct ports after expansion or the request is rejected.22,23,25,53,80,110,143,443,993,995
timeoutNoPer-port TCP connect timeout in seconds. Values outside 1-30 are coerced to 3.
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the scan completed.
hostNoThe submitted target host, echoed back.
target_ipNoThe resolved publicly-routable IP the scan was pinned to.
ports_scannedNoNumber of ports probed.
timeoutNoPer-port timeout in seconds actually used.
resultsNoOne entry per scanned port.
summaryNoAggregate counts across all probed ports.
warningsNoAdvisory notices about logging, authorization, and rate limits.
timestampNoISO 8601 completion time.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that it makes outbound connections, resolves to public IP only, rejects private ranges, is rate-limited (1/min, 5/hr, 20/day), may be logged, and requires permission. These details are not present in annotations, providing valuable transparency beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with purpose. While slightly verbose, each sentence adds necessary information. Could be marginally trimmed, but overall effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, output schema, annotations), the description covers behavioral aspects, usage guidelines, permission requirements, and output format. It is fully complete for an AI agent to understand and use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already describes all parameters. The description adds no extra detail on parameters beyond what the schema provides, but it contextualizes the tool's behavior. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs a TCP connect port scan, probing a live host for open TCP ports. It distinguishes itself from the sibling tool network_tcp_udp_port_reference by emphasizing live probing versus offline lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool ('detect actually-listening services on a host you control') and when to use the alternative (network_tcp_udp_port_reference for offline lookup). Also includes permission requirements and rate limits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server