Proxmint MCP server

• Registry namecom.proxmint/mcpverified in the MCP registry

The registry name sits under proxmint.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-19
• Tools6
• Server calls itselfproxmint
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 90 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score88 of 100answers 100 · definitions 100 · context 100 · use 8 · connects 100
• Use1 GitHub stars
• Answered100% of days15 of 15 daily checks
• Median first answer291 ms
• Space in an agent's context≈ 1,117 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_pricing

  Regular Proxmint pack prices for each proxy product: pack size, price and price per GB. Packs are prepaid, never expire, and are paid in crypto. No API key needed.

• get_account

  Wallet balance and every product on the account, with its status, bandwidth used and left, and the proxy host, ports and username. The proxy password is left out; generate_proxies returns ready-to-use lines.

• get_usage

  Bandwidth and requests per product per UTC day, oldest first, with totals per product. Days with no traffic are left out.

• generate_proxies

  Build proxy lines for one product, with optional location targeting and sticky sessions. Rotating lines get a new IP on every request; each sticky line keeps one IP for sticky_minutes (1-120). The lines include the proxy password.

• check_connection

  Send one request through a product's proxy and report the exit IP, the country Cloudflare sees it in, and the time taken. Uses a few kilobytes of the product's bandwidth.

• fetch_url

  Fetch one web page through a product's proxy, so the request leaves from that product's IPs and targeting: status, final URL (up to 5 redirects), title, and the page as readable text or raw HTML, cut at 50,000 characters. Each call gets a…