Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_proxy_detect

Probe saved proxies or an unsaved host:port to detect exit IP, location, and timezone; batch saved proxy IDs and write results back without exposing credentials.

Instructions

Probe saved proxy resources or an unsaved host:port for exit IP, location, and timezone. Pass proxyIds to check several saved proxies in one call. Results for saved proxies are written back like the Desktop proxy center. Credentials are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nex_proxy_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias of proxyId
hostNo
portNoProxy port
proxyIdNoSaved proxy ID to detect; omit when passing host and port
passwordNoWrite-only
protocolNoSOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating
proxyIdsNoSaved proxy IDs to detect in one call (up to 50); use this instead of repeated single calls
usernameNoWrite-only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2026.11.3
    • removedInput schema / properties / id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / id / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / port / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / port / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / proxyId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / proxyId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / proxyIds / items / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / proxyIds / items / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed5 schema fields changedv2026.10.24
    • changedInput schema / properties / id / description
      Previous value: -"Documented alias of proxyId"New value: +"Alias of proxyId"
    • changedInput schema / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / protocol / description
      Previous value: -"SOCKS5, HTTP, or HTTPS; omitted create defaults to SOCKS5"New value: +"SOCKS5, HTTP or HTTPS; defaults to SOCKS5 when creating"
    • addedInput schema / properties / proxyIds
      Added value: +{
      +  "description": "Saved proxy IDs to detect in one call (up to 50); use this instead of repeated single calls",
      +  "items": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "number"
      +      }
      +    ]
      +  },
      +  "maxItems": 50,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / username / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing that results for saved proxies are written back like the Desktop proxy center and that credentials are never returned. However, it does not explain the scope of the write-back, whether existing fields are overwritten, authentication requirements, rate limits, or failure behavior, leaving meaningful gaps for a probing tool with side effects.

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 three tight sentences with no filler, and the core operation is front-loaded. Each sentence contributes useful information about what is probed, batching, write-back, or credential handling.

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

Completeness3/5

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

For a tool with eight optional parameters, no annotations, and no output schema, the description covers the core operation and one important side effect. It remains incomplete about the exact return shape for exit IP, location, and timezone, and about how the optional parameters must be combined for a valid probe.

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 high at 88%, so the schema already documents proxyIds batching, write-only credentials, and protocol defaults. The description adds a little context about saved versus unsaved targets, but it still does not clarify the required combination of parameters or whether proxyId/id and host/port are mutually exclusive.

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

Purpose4/5

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

The description uses a specific verb, "Probe," and clearly names the resource: saved proxy resources or an unsaved host:port. It also states the key outputs, exit IP, location, and timezone, which makes the tool's purpose distinguishable from general proxy management siblings, though it does not explicitly name an alternative tool.

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

Usage Guidelines3/5

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

The description indicates two supported modes, saved proxies and unsaved host:port, and recommends proxyIds for batching saved proxies. It does not say when to use this instead of nex_proxy_list, nex_browser_connection_info, or other proxy-related siblings, nor does it state exclusions or prerequisites.

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

Deploy Server

Other Tools