BorrowIP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| borrowip_statusA | Check BorrowIP status. ALWAYS run this first. Returns the pair code (for connecting a phone) and lists connected proxies with their SOCKS5 ports. Example output: BorrowIP Status Pair code: BIP-ab12cd Proxies: 1 connected BIP-xw9su6 | socks5://127.0.0.1:10002 | IP: 140.213.141.84 | alive If no proxies: tells you the exact Termux command to run. |
| borrowip_get_proxyA | Get a ready-to-use SOCKS5 proxy URL. Returns the proxy URL string directly (e.g. 'socks5://127.0.0.1:10002'). Use this URL with any tool that accepts a proxy parameter:
Args: key: Optional connection code (e.g. BIP-xxxxxx). If omitted, uses first available. |
| borrowip_fetchA | Fetch a URL through the mobile proxy. Use when a website blocks your server/VPS IP (Cloudflare, rate limits, geo-blocks). The request goes through the phone's cellular connection instead. Args: url: The URL to fetch key: Optional connection code. If omitted, uses first available proxy. |
| borrowip_check_ipA | Check the external IP address of the mobile proxy. Useful to verify the proxy is working and see which IP/cellular network is being used. Args: key: Optional connection code. If omitted, uses first available proxy. |
| borrowip_list_proxiesA | List all connected mobile proxies with details. Returns one line per proxy: code, SOCKS5 URL, IP, age, alive status. |
| borrowip_health_checkA | Quick liveness check — is the proxy tunnel actually working? Tests if the SOCKS5 port is open AND can reach the internet. Much faster than borrowip_fetch (3s timeout vs 30s). Args: key: Optional connection code. If omitted, checks first available proxy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: checking IP, fetching, getting proxy URL, health check, listing, and status. No two tools perform the same function, making it clear for an agent which tool to use.
All tools start with 'borrowip_', but the suffix patterns vary: verb_noun (check_ip, get_proxy, list_proxies), verb only (fetch), noun (status), and compound noun (health_check). This inconsistency could confuse an agent slightly.
With 6 tools, the set is well-scoped for a proxy management server. Each tool serves a necessary function without being too few or too many.
The tools cover core proxy workflows: connecting (via status), listing, validating (check_ip, health_check), and using (fetch, get_proxy). Missing a dedicated disconnect tool is a minor gap but agents can work around it.