Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_proxy_list_more

Read-onlyIdempotent

Reveal hidden proxy rows beyond the first 50 from the Free Proxy List. Uses reCAPTCHA v3 to unlock up to 200 rows of pre-rendered HTML table data.

Instructions

Free Proxy List (Load More). Reveal the remaining rows of the Free Proxy List beyond the first 50 the page renders for everyone, for the current filter view. This is the captcha-gated "load more" companion to the server-rendered network_proxy_list page (which has no list-fetch API of its own): one reCAPTCHA v3 solve unlocks the rest of that view (session-scoped, ~30 min) up to a hard cap of 200 rows. Reads alive, public, credential-free proxies from this site's own already-checked database — it does not crawl or connect out to proxies at call time. Read-only and non-destructive, rate-limited (anonymous 10/min, 60/hour, 200/day). Returns pre-rendered HTML table rows (not structured JSON proxy objects), the row count, and a done flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNoThe active list filters identifying which view to page. Must match the filters used for the initial page render so the unlock and offset align.
tokenNoreCAPTCHA v3 response token (action "proxy_list_load_more"). Required only on the first reveal of a filter view; may also be sent via the X-Captcha-Response header. Omit once the view is unlocked for the session.
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when rows were returned (false with a 403 status when captcha verification is required).
htmlNoPre-rendered HTML table rows for the proxies beyond the initial 50, ready to append to the list.
countNoNumber of additional proxy rows included in html.
doneNoAlways true; all remaining rows (up to the 200 cap) are returned in one call, so there is nothing further to page.
Behavior5/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description reinforces this by stating it is read-only, non-destructive, does not crawl proxies, and adds concrete rate limits and session scope. No 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 a single, dense paragraph that front-loads the core purpose and covers all critical details without unnecessary fluff. Every sentence adds 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?

Given the tool's complexity (captcha, session limits, rate limits, output format), the description addresses all key aspects. It mentions the output format (HTML rows, count, done flag) even though an output schema exists. No gaps.

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?

All parameters have schema descriptions (100% coverage). The description adds meaningful context: token required only on first reveal, filters must match initial view, and alternative header method. This goes beyond schema definitions.

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's purpose: revealing additional rows of the Free Proxy List beyond the initial 50. It specifies the resource, action, and constraints (captcha-gated, 200-row cap), and differentiates from the companion tool network_proxy_list.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to load more than 50 rows) and prerequisites (matching filters, reCAPTCHA token on first call). It implies when not to use (e.g., when initial page suffices), though not explicit. Alternatives are implied via sibling context.

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