OnlineCyberTools MCP (280+ filterable tools)

network_tcp_udp_port_reference

Read-onlyIdempotent

Look up TCP and UDP port assignments from a built-in database of well-known and registered network services. Filter by service name, protocol, numeric range, or category to identify port numbers.

Instructions

TCP/UDP Port Reference Lookup. Look up TCP and UDP port assignments from a built-in static database of well-known and registered network services (HTTP, HTTPS, SSH, FTP, DNS, SMTP, databases, VPNs, games, and more). Filter by free-text query, protocol, numeric range, or service category and get matching port records with service name, description, and any security note. Use this for offline port-number and service identification; use network_port_scanner instead to probe a live host for actually-open ports. Read-only, non-destructive, contacts no external service (queries an in-memory table), and rate-limited (30 req/min, 180/hr anonymous). Returns the full match list, a limit-capped display slice, and TCP/UDP and range summary counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`search`	Yes	Free-text query matched against port number, service name, description, and category (case-insensitive substring). The special form "tcp:443" or "udp:53" matches one exact protocol+port. Empty string returns all ports (subject to the other filters).
`protocol`	No	Restrict results to one transport protocol. all returns both TCP and UDP. Case-insensitive.	all
`range`	No	Restrict by port range: well-known 0-1023, registered 1024-49151, dynamic 49152-65535, or all.	all
`category`	No	Restrict to one service category, or all for every category.	all
`limit`	No	Maximum number of records returned in displayedPorts. Non-positive or non-numeric values fall back to 50. Does not cap total or ports.
`worker_id`	No	Optional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when the lookup succeeded.
`search`	No	Normalised (trimmed) search query that was applied.
`protocol`	No	Normalised (lowercased) protocol filter that was applied.
`range`	No	Range filter that was applied.
`category`	No	Category filter that was applied.
`total`	No	Total number of port records matching the filters (before the limit slice).
`ports`	No	All matching port records, sorted by port number then protocol.
`displayedPorts`	No	First limit records of ports, for paginated display.
`stats`	No	Aggregate counts over the matched ports.
`error`	No	Error message when success is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / category / default
```
Added value: +"all"
```

addedInput schema / properties / category / description

Added value: +"Restrict to one service category, or all for every category."

addedInput schema / properties / category / enum

Added value: +[
+  "all",
+  "web",
+  "email",
+  "file",
+  "database",
+  "security",
+  "game",
+  "other"
+]

addedInput schema / properties / limit / default
```
Added value: +50
```

addedInput schema / properties / limit / description

Added value: +"Maximum number of records returned in displayedPorts. Non-positive or non-numeric values fall back to 50. Does not cap total or ports."

addedInput schema / properties / limit / minimum
```
Added value: +1
```
addedInput schema / properties / protocol / default
```
Added value: +"all"
```

addedInput schema / properties / protocol / description

Added value: +"Restrict results to one transport protocol. all returns both TCP and UDP. Case-insensitive."

addedInput schema / properties / protocol / enum

Added value: +[
+  "all",
+  "tcp",
+  "udp"
+]

addedInput schema / properties / range / default
```
Added value: +"all"
```

addedInput schema / properties / range / description

Added value: +"Restrict by port range: well-known 0-1023, registered 1024-49151, dynamic 49152-65535, or all."

addedInput schema / properties / range / enum

Added value: +[
+  "all",
+  "well-known",
+  "registered",
+  "dynamic"
+]

addedInput schema / properties / search / default
```
Added value: +""
```

addedInput schema / properties / search / description

Added value: +"Free-text query matched against port number, service name, description, and category (case-insensitive substring). The special form \"tcp:443\" or \"udp:53\" matches one exact protocol+port. Empty string returns all ports (subject to the other filters)."

addedInput schema / properties / search / examples
```
Added value: +[
+  "https",
+  "tcp:22"
+]
```

changedInput schema / required

Previous value: -[
-  "search",
-  "protocol",
-  "range",
-  "category",
-  "limit"
-]New value: +[
+  "search"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "description": "Category filter that was applied.",
+      "type": "string"
+    },
+    "displayedPorts": {
+      "description": "First limit records of ports, for paginated display.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error message when success is false.",
+      "type": "string"
+    },
+    "ports": {
+      "description": "All matching port records, sorted by port number then protocol.",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Service category (web, email, file, database, security, game, other).",
+            "type": "string"
+          },
+          "description": {
+            "description": "Human-readable description of the service.",
+            "type": "string"
+          },
+          "port": {
+            "description": "Port number 0-65535.",
+            "type": "integer"
+          },
+          "protocol": {
+            "description": "Transport protocol, TCP or UDP.",
+            "type": "string"
+          },
+          "security": {
+            "description": "Optional security note (present only for some ports, e.g. \"Insecure - use SSH instead\").",
+            "type": "string"
+          },
+          "service": {
+            "description": "Service or application name (e.g. SSH, HTTPS).",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "protocol": {
+      "description": "Normalised (lowercased) protocol filter that was applied.",
+      "type": "string"
+    },
+    "range": {
+      "description": "Range filter that was applied.",
+      "type": "string"
+    },
+    "search": {
+      "description": "Normalised (trimmed) search query that was applied.",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Aggregate counts over the matched ports.",
+      "properties": {
+        "dynamic": {
+          "description": "Matched ports in 49152-65535.",
+          "type": "integer"
+        },
+        "registered": {
+          "description": "Matched ports in 1024-49151.",
+          "type": "integer"
+        },
+        "tcp": {
+          "description": "Number of matched TCP records.",
+          "type": "integer"
+        },
+        "udp": {
+          "description": "Number of matched UDP records.",
+          "type": "integer"
+        },
+        "wellKnown": {
+          "description": "Matched ports in 0-1023.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the lookup succeeded.",
+      "type": "boolean"
+    },
+    "total": {
+      "description": "Total number of port records matching the filters (before the limit slice).",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds useful context beyond that: it mentions the tool is read-only, non-destructive, uses an in-memory table (no external service), and has rate limits (30 req/min, 180/hr). This adds value but the annotations already cover core safety.

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

Conciseness5/5

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

The description is concise and well-structured: it starts with the core purpose, then details filtering capabilities, provides usage contrast, and ends with behavioral and rate-limit info. Every sentence contributes value without redundancy.

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?

Despite having an output schema, the description explicitly lists what is returned (service name, description, security note, full match list, display slice, summary counts), ensuring the agent understands the response structure. It covers all key aspects for a tool of this complexity.

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 description coverage is 100%, so the baseline is 3. The description does not add significant new meaning beyond what the parameter descriptions provide; it restates or summarizes them. No added depth.

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's purpose: 'TCP/UDP Port Reference Lookup' and explicitly contrasts with network_port_scanner for probing live hosts, making its unique function unmistakable.

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?

Provides explicit guidance on when to use this tool ('offline port-number and service identification') and when not to ('use network_port_scanner instead to probe a live host for actually-open ports'), including a named alternative.

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

Deploy Server