ProxyJam

com.proxyjamPublished by proxyjam.comOfficial publisherv3.3.1Updated Oct 27, 2026

Buy and manage ISP proxies: offers, orders, renewals, traffic, whitelists and wallet.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for ProxyJam that lets an assistant buy and manage ISP proxies: offers, orders, renewals, traffic, whitelists and wallet.

What you can do
  • Browse ISP proxy offers and place or manage orders
  • Renew existing proxy subscriptions
  • Check traffic usage and account wallet balance
  • Manage IP whitelists for proxy access
When to use it
Useful when you want an assistant to handle ProxyJam ISP proxy purchasing and account upkeep, such as comparing offers, ordering or renewing proxies, checking traffic and wallet balance, or adjusting whitelists, without leaving the chat.
Requirements
A remote MCP endpoint at proxyjam.com over streamable HTTP. A ProxyJam account is needed, authenticated either with OAuth or with an API key sent in the X-API-Key header. No local runtime or packages are required.
Before you install
The server can spend money: ordering and renewing proxies draw on the account wallet, so confirm costs before letting an assistant act. It also changes account state through orders and whitelist edits. The API key in X-API-Key is a secret; prefer OAuth sign-in and keep the key out of shared logs.

Installation

In SourceWeft

  1. Open ProxyJam 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/com.proxyjam%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": {
    "proxyjam": {
      "type": "http",
      "url": "https://proxyjam.com/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. v3.3.1LatestOct 20, 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.