Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

security_proxy_parse

Read-onlyIdempotent

Parse a newline-separated proxy list into structured records, extracting protocol, host, port, and optional credentials for validation.

Instructions

Proxy List Parser. Parse a newline-separated proxy list into structured records, splitting each line into protocol, host, port, and optional username/password. Use this to validate and normalise proxy input before testing; use security_proxy_test (or its streaming variant) when you actually want to connect to and benchmark the proxies. Pure local text parsing: read-only, non-destructive, contacts no proxy or external service, and rate-limited (anonymous 2/min, 10/hour, CAPTCHA after 5/hour). Returns the parsed valid proxies, per-line parse errors, and counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proxiesYesNewline-separated proxy list. Each non-empty line must match [protocol://][user:pass@]host:port (protocol defaults to http; port 1-65535). Blank lines and lines starting with # are skipped.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200 response.
dataNoParsed output payload.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / options
      Removed value: -{
-  "properties": {
-    "concurrency": {
-      "type": "integer"
-    },
-    "retryAttempts": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "concurrency",
-    "retryAttempts"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / proxies / description
      Added value: +"Newline-separated proxy list. Each non-empty line must match [protocol://][user:pass@]host:port (protocol defaults to http; port 1-65535). Blank lines and lines starting with # are skipped."
    • addedInput schema / properties / proxies / examples
      Added value: +[
+  "http://1.2.3.4:8080\nuser:pass@5.6.7.8:1080"
+]
    • changedInput schema / required
      Previous value: -[
-  "proxies",
-  "options"
-]New value: +[
+  "proxies"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Parsed output payload.",
+      "properties": {
+        "error_count": {
+          "description": "Number of entries in parse_errors.",
+          "type": "integer"
+        },
+        "parse_errors": {
+          "description": "One entry per line that failed to parse.",
+          "items": {
+            "properties": {
+              "error": {
+                "description": "Reason, e.g. \"Invalid proxy format\".",
+                "type": "string"
+              },
+              "line": {
+                "description": "1-based line number of the bad entry.",
+                "type": "integer"
+              },
+              "text": {
+                "description": "The offending trimmed line text.",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "total_lines": {
+          "description": "Total lines in the input, including blanks and comments.",
+          "type": "integer"
+        },
+        "valid_count": {
+          "description": "Number of entries in valid_proxies.",
+          "type": "integer"
+        },
+        "valid_proxies": {
+          "description": "Successfully parsed proxies, in input order.",
+          "items": {
+            "properties": {
+              "host": {
+                "description": "Proxy host or IP.",
+                "type": "string"
+              },
+              "line_number": {
+                "description": "1-based line number in the input.",
+                "type": "integer"
+              },
+              "original": {
+                "description": "The trimmed source line, as supplied.",
+                "type": "string"
+              },
+              "password": {
+                "description": "Auth password if present, else null.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "port": {
+                "description": "Proxy port (1-65535).",
+                "type": "integer"
+              },
+              "protocol": {
+                "description": "Scheme parsed from the line, or \"http\" when omitted.",
+                "type": "string"
+              },
+              "username": {
+                "description": "Auth username if present, else null.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Always true on a 200 response.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already set readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds valuable context: pure local parsing, no external contacts, and rate limits (2/min, 10/hour, CAPTCHA after 5/hour). This enriches behavioral understanding without contradiction.

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 four concise sentences: title-like opener, operational detail, usage guidance with alternatives, and behavioral constraints. No extraneous information; every sentence provides essential value.

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?

The description covers purpose, when to use, behavioral traits (local, rate limits), and output summary (parsed proxies, parse errors, counts). Although an output schema exists, the description adequately summarizes return values without redundancy.

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

Parameters4/5

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

The single parameter (proxies) has 100% schema description coverage. The description adds extra meaning by specifying the expected format (protocol://user:pass@host:port, defaults to http, port range 1-65535) and skipping rules (blank lines, # comments), exceeding the schema's examples.

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 identifies the tool as a parser for proxy lists, specifying the action (parse) and the resource (newline-separated proxy list). It details the output structure (protocol, host, port, optional credentials) and distinguishes from siblings by explicitly naming security_proxy_test for actual connections.

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?

The description provides explicit guidance on when to use this tool (validate/normalize before testing) and when to use alternatives (security_proxy_test for connecting/benchmarking), making the selection decision clear.

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