Skip to main content
Glama
NovadaLabs

novada-mcp

Official
by NovadaLabs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

novada_proxy_residential

Read-onlyIdempotent

Route requests through residential IPs to bypass anti-bot protections and access geo-restricted content. Supports country and city targeting for precise geo-location.

Instructions

Route requests through residential IPs — real home ISP addresses from a 100M+ IP pool. Best anti-bot bypass for geo-restricted or protected pages.

Best for: Anti-bot protected pages, geo-restricted content, platforms that block datacenter IPs. Not for: novada_extract or novada_crawl — they handle proxy routing internally. These credentials are for your own HTTP clients (curl, requests, axios). Params: url (optional), country (ISO 2-letter), city (optional, requires country), session_id (optional for sticky IP). Formats: "url", "env", "curl". agent_instruction: Best for geo-restricted content. Use country param for targeting. Strongest anti-bot bypass — escalate here from isp/datacenter when blocked. Requires: NOVADA_PROXY_USER, NOVADA_PROXY_PASS, NOVADA_PROXY_ENDPOINT env vars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoOptional target URL to route through the proxy. When provided, returns config scoped for that URL. Omit to get generic proxy credentials.
countryNoISO 2-letter country code for geo-targeting (e.g. 'us', 'gb', 'de'). Best for geo-restricted content.
cityNoCity-level targeting (e.g. 'london', 'new-york'). Requires country to be set.
session_idNoSession ID for sticky IP routing — same session_id returns the same residential IP across requests.
formatYesOutput format. 'url': proxy URL string (default). 'env': shell export commands. 'curl': curl --proxy flag.url

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint. Description adds environment variable requirements and notes that the tool returns proxy config for external clients, not internal use. No contradictions with annotations.

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?

Well-structured with clear sections (Best for, Not for, Params, Formats, Requires). Every sentence is informative. No redundancy.

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?

Covers purpose, usage, parameter details, and environment setup. Although no output schema, the formats parameter explains possible return values. Could mention if other parameters are required for certain formats, but overall sufficient.

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?

Schema coverage is 100% with good per-parameter descriptions. The description adds a summary and clarifies the relationship between city and country (requires country). This adds value beyond the schema.

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 states the tool routes requests through residential IPs for anti-bot bypass and geo-restricted content. It distinguishes from sibling tools like novada_proxy_datacenter and novada_proxy_isp by specifying 'real home ISP addresses' and 'best anti-bot bypass'.

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 lists best use cases (anti-bot protected, geo-restricted) and what not to use it for (novada_extract/crawl handle proxy internally). Provides escalation guidance ('escalate here from isp/datacenter when blocked').

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/NovadaLabs/novada-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server