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.

agproxy

REMOTE · AGPROXY.SHVEIK.DEV

Residential proxy traffic and raw fetch for agents, 190+ countries, sticky sessions. Pay per call.

+7 this week 79 Trust /100

Last scanned (23 hours ago)

Scores higher than 82% of remote servers

Reachable. Last reached 16 Oct 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 Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 735 tokens (~105/item across 7 items; 3 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 16 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.

  • 14 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 10 Oct 26 +4
    • Schema quality: fail → pass ▲ functional
    • First check of Schema quality: 100 functional
  • 7 Oct 26 72

    First indexed and scored.

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 16 Oct 2026 · Probed https://agproxy.shveik.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agproxy.shveik.dev CN=YE1,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA384 6368a9254250c26f8500e66216005e67e8c
SANs: agproxy.shveik.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agproxy.shveik.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
shveik.dev. 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=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agproxy.shveik.dev/mcp Verified 200
http (plaintext) http://agproxy.shveik.dev/mcp HTTPS enforced 308 https://agproxy.shveik.dev/mcp
MCP tools · 3 exposed · ~480 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
feedback ~117

Free. Tell the people who run this service what worked, what failed or what you miss: a bug, an idea or a thanks. A person reads it. No payment, no account; limited to a few messages an hour.

NameTypeReqDescription
contactstring–optional: how we can reach you or your operator
kindstring––
messagestringyeswhat worked, what did not, what you miss; no secrets or private data
routestring–the route the feedback is about, if any

No output schema declared.

No examples provided.

fetch ~210

Fetch one URL from a residential IP and get the raw response as JSON: status, final URL, headers and body (text or base64), up to 10 MB. GET, HEAD or POST, your own headers, an optional country. No JavaScript rendering. You pay for the megabytes delivered; a fetch that fails is not charged. Pay per call in stablecoins. Not offered on Solana: pay on Base or Polygon.

NameTypeReqDescription
bodystring–request body for POST, sent as given
countrystring–exit country, a two-letter code such as DE or US (default: anywhere)
headersobject–request headers; Host, Content-Length, Connection, Accept-Encoding and proxy headers are set by the service
max_mbinteger–most megabytes of the response to return and pay for; a longer body is cut and flagged truncated
methodstring––
urlstringyesthe http or https URL to fetch

No output schema declared.

No examples provided.

proxy ~153

Residential proxy for AI agents. Pay for gigabytes of traffic and get a proxy login (host, port, username, password) after payment, to use with curl, a browser or any HTTP client. Choose a country, rotate the IP on every connection or keep one with a session tag. A pack lasts 90 days. Pay per pack in stablecoins. Not offered on Solana: pay on Base or Polygon.

NameTypeReqDescription
countrystring–optional default exit country, a two-letter code such as DE or US; the username can override it per connection
gbinteger–gigabytes of traffic in the pack (1 GB = 1,000,000,000 bytes, counted on both directions)

No output schema declared.

No examples provided.

Install

How do I install the agproxy MCP server?

agproxy is a hosted endpoint at https://agproxy.shveik.dev/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 · agproxy.shveik.dev

# add to Claude Code
claude mcp add --transport http dev-shveik-agproxy 'https://agproxy.shveik.dev/mcp'
Common questions

What is the agproxy MCP server?

agproxy is an MCP server listed in the public MCP registry as dev.shveik/agproxy. Residential proxy traffic and raw fetch for agents, 190+ countries, sticky sessions. Pay per call. This page covers its hosted endpoint (https://agproxy.shveik.dev/mcp).

Is the agproxy MCP server safe to use?

agproxy scores 79 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 agproxy MCP server expose?

agproxy exposes 3 tools: proxy, fetch, feedback. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.

Does the agproxy MCP server require authentication?

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

Is the agproxy MCP server still maintained?

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