Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nex_proxy_detect

Probe saved proxies or a host:port to detect exit IP, location, and timezone, and batch-check up to 50 saved proxy IDs in one call.

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.

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. 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"
  2. Addedv2026.8.20

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that results for saved proxies are written back like the Desktop proxy center (a mutation side effect) and that credentials are never returned. It omits failure behavior, timeouts, and whether proxy authentication is required, which are meaningful gaps for a network-probing tool.

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?

Three tightly written sentences with zero waste. The primary capability is front-loaded, followed by the batch shortcut and the security/side-effect note.

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

Completeness4/5

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

For an 8-parameter tool with no output schema and no annotations, the description covers the key unknowns: what is returned, that saved-proxy results are written back, batch behavior, and that credentials are not exposed. It could say more about errors or prerequisites, but an agent has enough to call it correctly.

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 most parameters, including proxyId, proxyIds, protocol, and write-only credentials. The description adds only the batch-use hint for proxyIds and the saved-vs-unsaved distinction, which the schema largely covers already; 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?

The description uses a specific verb ('Probe') and clearly names both modes: saved proxy resources and an unsaved host:port. It also states the returned data (exit IP, location, timezone), so an agent can distinguish this from sibling tools like nex_proxy_list or nex_proxy_create without opening any schema.

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?

It gives clear context: use saved proxies or an unsaved host:port, and pass proxyIds to check several saved proxies in one call. However, it does not explicitly name alternatives (e.g., nex_proxy_list) or state when not to use this tool, leaving some inference to the agent.

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