prokso
Registry code: f838ef100e920975
Prokso sells residential, mobile and datacenter proxies billed per GB. Use list_plans to see the user's plans, then get_proxy_lines to get ready-to-use proxy strings (host gw.prokso.com; port 823 HTTP and 824 SOCKS5 give a new IP per request, ports 10000-20000 keep one IP for 1-120 minutes). Precise geo (state, city, ZIP, ASN) counts traffic double. These tools never spend money; buying traffic is done in the dashboard or via the REST API.
- endpoint
- https://prokso.com/api/v1/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is prokso live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is prokso free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does prokso have?
- 5 tools: list_plans, get_proxy_lines, get_account, get_prices, get_plan.
- Is prokso safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_plans auth-required never probed
List all proxy plans on the account with id, label, proxy type, status (active, paused or limited) and remaining traffic. Call it first to find the plan_id that get_plan and get_proxy_lines need. Takes no arguments; read-only.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_proxy_lines auth-required 1h ago
Generate ready-to-use proxy strings for a plan. session='rotating' returns one line whose IP changes on every request (ports 823/824); session='sticky' gives one IP per port for 1-120 minutes (ports from 10000). Optional country (ISO code such as 'us' or 'de', several comma-separated), and for precise geo state, city, zip or asn (counts traffic double). Availability of a specific city or provider is not guaranteed.
{ "type": "object", "required": [ "plan_id" ], "properties": { "asn": { "type": "string", "description": "Provider ASN number, e.g. '7922'." }, "zip": { "type": "string" }, "city": { "type": "string", "description": "City name in Latin letters, e.g. 'newyorkcity'." }, "count": { "type": "integer", "default": 5, "maximum": 100, "minimum": 1 }, "state": { "type": "string", "description": "US state, e.g. 'texas'." }, "format": { "enum": [ "lp@hp", "hp:lp", "url", "hp@lp", "lp:hp", "hp" ], "type": "string", "default": "lp@hp", "description": "lp@hp = login:password@host:port, hp:lp = host:port:login:password, url = protocol://login:password@host:port" }, "country": { "type": "string" }, "plan_id": { "type": "integer", "description": "Plan id from list_plans." }, "session": { "enum": [ "rotating", "sticky" ], "type": "string", "default": "sticky" }, "protocol": { "enum": [ "http", "socks5" ], "type": "string", "default": "http" } }, "additionalProperties": false }arguments 66 linesget_account auth-required 1h ago
Get the email of the Prokso account this API key belongs to and its current balance in USD (in cents and formatted). Use it to confirm the account or before suggesting a purchase. Takes no arguments; read-only, never spends money.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_prices auth-required 1h ago
Get current prices per GB for residential, mobile and datacenter proxies, including volume tiers and the minimum order when paying from the balance. Use it to estimate the cost of a task; it does not buy anything. Takes no arguments.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_plan auth-required never probed
Get full connection details for one plan: login, password, gateway host, ports (823 HTTP and 824 SOCKS5 with a new IP per request, 10000-20000 for a sticky IP) and remaining traffic. Use it when you need the credentials to configure a client yourself; for ready-made proxy strings use get_proxy_lines. The result contains the plan password, so show it only to the account owner. Returns an error result if plan_id does not exist or belongs to another account.
{ "type": "object", "required": [ "plan_id" ], "properties": { "plan_id": { "type": "integer", "description": "Plan id from list_plans." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf838ef100e920975.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f838ef100e920975/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f838ef100e920975?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.