ProxyEmpire

io.proxyempirePublished by proxyempire.ioOfficial publisherv1.0.0Updated Nov 8, 2026

Check proxy balances, generate geo-targeted proxy lists, diagnose 407s, and manage sub-users.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

ProxyEmpire's remote MCP server lets an assistant check proxy balances, build geo-targeted proxy lists, troubleshoot 407 errors, and manage sub-users.

What you can do
  • Check proxy account balances and usage.
  • Generate proxy lists filtered by geographic target.
  • Diagnose 407 proxy authentication errors.
  • Manage sub-users on the account.
When to use it
Useful when an assistant helps operate a ProxyEmpire proxy account: reviewing balances, assembling geo-targeted proxy lists for a task, troubleshooting 407 authentication failures, or administering sub-users.
Requirements
A remote MCP endpoint at panel.proxyempire.io with OAuth sign-in required; no packages, environment variables, or headers are declared.
Before you install
OAuth grants the assistant access to a paid proxy account, including balance information and sub-user management, so changes made through it affect real account resources and billing. No write, delete, or third-party data-sharing behavior is described in the available material.

Installation

In SourceWeft

  1. Open ProxyEmpire in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.proxyempire%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "proxyempire": {
      "type": "http",
      "url": "https://panel.proxyempire.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.