About atheris-mcp
atheris-mcp is an MCP server for agents that need to route traffic through Atheris mobile or residential proxies in a chosen country. It provides live capacity, ready-to-use proxy URLs, and account usage through tools.
Key features
- 01Check live proxy stock by country and pool
- 02Create HTTP or SOCKS5 proxy URLs
- 03Choose session and rotation behavior
- 04Check remaining data and expiry
Use cases
- 01Select a country and proxy pool with available capacity
- 02Route HTTP client traffic through a country-specific IP
- 03Track remaining proxy data and key expiry
MCP support
Exposes stock, proxy URL, and usage checks as tools for MCP clients. Proxy URL and usage calls require an Atheris access key.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y atheris-mcpATHERIS_PROXY_KEYSecretAtheris pak_ access key (required for atheris_proxy_url and atheris_usage; atheris_stock works without it)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project READMEatheris-mcp
An MCP server for Atheris proxies — real-carrier 4G/5G mobile and residential IPs, per gigabyte. It gives an agent a fully autonomous path to route traffic through a specific-country IP: check live stock, get a ready-to-use proxy URL, and check remaining GB — all as tool calls.
Zero dependencies. One file. Node ≥ 18.
Tools
atheris_stock— live proxy stock by country and pool (mbl= mobile,peer= residential). No key needed. Call it first to pick a country with capacity.atheris_proxy_url— a readyhttp://orsocks5://proxy URL for a country/pool/session/rotation. Hand it straight to any HTTP client.atheris_usage— the key's remaining GB and expiry.
Setup
You need an Atheris access key (pak_…) from the dashboard.
From npm (atheris-mcp, also in the
official MCP registry as io.github.atheris-ee/atheris-mcp):
// Claude Desktop / Claude Code / Cursor / any MCP client
{
"mcpServers": {
"atheris": {
"command": "npx",
"args": ["-y", "atheris-mcp"],
"env": { "ATHERIS_PROXY_KEY": "pak_your_key_here" }
}
}
}
Straight from GitHub also works: "args": ["-y", "github:atheris-ee/atheris-mcp"].
Or from a local checkout:
{
"mcpServers": {
"atheris": {
"command": "node",
"args": ["/path/to/atheris-mcp.mjs"],
"env": { "ATHERIS_PROXY_KEY": "pak_your_key_here" }
}
}
}
Env:
ATHERIS_PROXY_KEY— your pak access key (required foratheris_proxy_urlandatheris_usage;atheris_stockworks without it).ATHERIS_API_BASE— defaults tohttps://atheris.ee/api/v1. Your key is sent as a Bearer token to whatever host this names, so only point it at a host you trust.
The key is the same credential used as the proxy password — treat it like one.
Keep it in env, not in command args, and rotate it from the dashboard if it
leaks. The server talks only to atheris.ee (or your ATHERIS_API_BASE) and
collects no telemetry.
The atheris_proxy_url result is also a secret. Both its proxy_url and
password fields embed your pak key — treat the tool's output like the key
itself: don't log it or paste it into shared transcripts.
Session rule (important)
Each atheris_proxy_url call takes a session id. The same session id returns the
same exit IP. For many parallel identities (scraping distinct hosts, running many
antidetect profiles), give each identity its own session id — reusing one sticky
session across many pins them all to a single exit. Use rotation: "hard" if you want
a fresh exit on every connection instead.
The underlying HTTP API
The server is a thin wrapper over the Atheris JSON API (bearer-authed with your pak key):
GET /api/v1/stockGET /api/v1/proxy?country=us&pool=mbl&session=<id>&rotation=sticky&protocol=httpGET /api/v1/usage
See https://atheris.ee/llms-full.txt for the full agent reference, including buying access programmatically.
License
MIT © Arvane Holdings OÜ
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.