Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

security_proxy_test

Test multiple proxy servers simultaneously for connectivity, speed, anonymity, and IP leakage. Get detailed results and statistics for each proxy.

Instructions

Proxy Tester (Batch). Test many proxy servers in one batch and return each result plus aggregate statistics. Every proxy is checked for HTTP/HTTPS connectivity, response speed, anonymity level, IP-leak, the outgoing IP it presents, and geographic location. Results are NOT cacheable: they reflect live network state and vary between calls. Use security_proxy_parse first to normalise raw input; use security_proxy_test_single to test exactly one proxy; use security_proxy_test_stream to stream incremental per-proxy results instead of waiting for the whole batch. This tool makes outbound network connections through each supplied proxy to fixed third-party endpoints (httpbin.org, ipify.org, ip-api.com, etc.); target URLs are not user-configurable. Rate-limited (anonymous 2/min, 10/hour, 30/day; CAPTCHA after 5/hour). Returns results[] (one full test record per proxy) and a statistics summary.

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; auth optional). Blank lines and lines starting with # are skipped. Lines that fail to parse are dropped; a 400 is returned only if no valid proxy remains.
optionsNoOptional test settings.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200 response.
dataNoAggregated batch output.
Behavior5/5

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

Discloses results not cacheable, makes outbound connections to fixed endpoints, target URLs not configurable, rate-limited with specific limits and CAPTCHA. This goes beyond annotations which only give hints.

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?

Single, dense paragraph that is front-loaded with purpose. Every sentence adds value; no wasted words.

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?

Covers purpose, usage, behavioral traits, rate limits, and alternatives. Output schema exists, so description doesn't need to detail return values. Complete for 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% with detailed descriptions for all parameters. The tool description adds minimal extra meaning beyond the schema, so 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?

Clearly states the tool batch-tests many proxy servers, listing specific checks (HTTP/HTTPS, speed, anonymity, IP leak, etc.). Distinguishes from siblings by mentioning batch vs single vs stream.

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 alternatives: use security_proxy_parse first to normalize input, security_proxy_test_single for one proxy, security_proxy_test_stream for incremental results. Also notes non-cacheable nature 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