Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Proxmint

REMOTE · PROXMINT.COM

Fetch pages through your proxies, plus proxy lines, balance, usage and pricing for Proxmint

Available components

+3 this week 80 Trust /100

Last scanned (1 hour ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 842 tokens (~140/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_connection" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • Server version: 1.0.0 → 1.1.0 functional
  • 31 Oct 26 0
    • Tool “get_account” rewrote its description, which is the text the model reads security
    • “generate_proxies” reworded the description of “format” cosmetic
  • 30 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_pricing” rewrote its description, which is the text the model reads security
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://proxmint.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=proxmint.com CN=WE1,O=Google Trust Services,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 e5a24ca6cc57637513d4082659c78155
SANs: proxmint.com, *.proxmint.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of proxmint.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
proxmint.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://proxmint.com/api/mcp Verified 200
http (plaintext) http://proxmint.com/api/mcp HTTPS enforced 301 https://proxmint.com/api/mcp
MCP tools · 6 exposed · ~692 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_connection ~91

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.

NameTypeReqDescription
countrystring–ISO 3166 alpha-2 country code, e.g. us. Leave every location field empty to use the targeting saved in the dashboard.
productstringyesProxy product

No output schema declared.

No examples provided.

fetch_url ~172

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 new exit IP. Uses the product's bandwidth for the bytes transferred; binary files are not read.

NameTypeReqDescription
countrystring–ISO 3166 alpha-2 country code, e.g. us. Leave every location field empty to use the targeting saved in the dashboard.
formatstring–text: readable text, with scripts, styles and tags removed. html: the raw markup
productstringyesProxy product
urlstringyesThe page to fetch: an http or https URL

No output schema declared.

No examples provided.

generate_proxies ~284

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.

NameTypeReqDescription
asnstring–Carrier or ISP network number (ASN), digits only. Needs country.
citystring–City, e.g. newyork. Needs country.
countinteger–Number of sticky lines, each with its own IP (rotating returns one line)
countrystring–ISO 3166 alpha-2 country code, e.g. us. Leave every location field empty to use the targeting saved in the dashboard.
formatstring–url: protocol://user:pass@host:port. host:port:user:pass: the colon format many tools import
productstringyesProxy product
protocolstring–http (also carries HTTPS) or socks5
sessionstring–rotating: a new IP on every request. sticky: each line keeps one IP for sticky_minutes
statestring–State or region, e.g. california. Needs country.
sticky_minutesinteger–How long each sticky line keeps its IP
zipstring–ZIP or postal code. Needs country.

No output schema declared.

No examples provided.

get_account ~42

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~51

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

NameTypeReqDescription
productstring–Only this product

No output schema declared.

No examples provided.

get_usage ~52

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

NameTypeReqDescription
daysinteger–Days back from today, today included (1-90)

No output schema declared.

No examples provided.

Install

How do I install the Proxmint MCP server?

Proxmint is a hosted endpoint at https://proxmint.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · proxmint.com

# add to Claude Code
claude mcp add --transport http com-proxmint-mcp 'https://proxmint.com/api/mcp'
Common questions

What is the Proxmint MCP server?

Proxmint is an MCP server listed in the public MCP registry as com.proxmint/mcp. Fetch pages through your proxies, plus proxy lines, balance, usage and pricing for Proxmint. This page covers its hosted endpoint (https://proxmint.com/api/mcp).

Is the Proxmint MCP server safe to use?

Proxmint scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Proxmint MCP server expose?

Proxmint exposes 6 tools: get_pricing, get_account, get_usage, generate_proxies, check_connection, fetch_url. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.

Does the Proxmint MCP server require authentication?

No. We connected to Proxmint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Proxmint MCP server still maintained?

Proxmint is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.