# agproxy (remote · agproxy.shveik.dev)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `agproxy.shveik.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-shveik-agproxy/agproxy.md), [page](https://verifymcp.io/servers/dev-shveik-agproxy/agproxy)

## Channel facts

- Endpoint: `https://agproxy.shveik.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 723 tokens (~103/item across 7 items; 3 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http dev-shveik-agproxy 'https://agproxy.shveik.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-shveik-agproxy": {
      "url": "https://agproxy.shveik.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-shveik-agproxy": {
      "type": "http",
      "url": "https://agproxy.shveik.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-shveik-agproxy]
url = "https://agproxy.shveik.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-shveik-agproxy": {
      "type": "remote",
      "url": "https://agproxy.shveik.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-shveik-agproxy --url 'https://agproxy.shveik.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-shveik-agproxy:
    url: "https://agproxy.shveik.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-shveik-agproxy": {
      "Transport": "http",
      "Url": "https://agproxy.shveik.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-shveik-agproxy -t streamable-http -u 'https://agproxy.shveik.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-shveik-agproxy": {
      "type": "http",
      "url": "https://agproxy.shveik.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 79, 0)

- [security] Tool “fetch” rewrote its description, which is the text the model reads

### 2026-10-16 (score 79, +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.

### 2026-10-14 (score 78, +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.

### 2026-10-12 (score 77, +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.

### 2026-10-10 (score 76, +4)

- [functional improvement] Schema quality: fail → pass
- [functional] First check of Schema quality: 100

### 2026-10-07 (score 72)

First indexed and scored.

## MCP tools (3)

### `proxy` (~153 tokens)

Residential proxy pack

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.

Input parameters:

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

### `fetch` (~198 tokens)

Raw fetch from a residential IP

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.

Input parameters:

- `body` (string): request body for POST, sent as given
- `country` (string): exit country, a two-letter code such as DE or US (default: anywhere)
- `headers` (object): request headers; Host, Content-Length, Connection, Accept-Encoding and proxy headers are set by the service
- `max_mb` (integer): most megabytes of the response to return and pay for; a longer body is cut and flagged truncated
- `method` (string)
- `url` (string, required): the http or https URL to fetch

### `feedback` (~117 tokens)

Send feedback

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.

Input parameters:

- `contact` (string): optional: how we can reach you or your operator
- `kind` (string)
- `message` (string, required): what worked, what did not, what you miss; no secrets or private data
- `route` (string): the route the feedback is about, if any

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-shveik-agproxy/agproxy#diagnostics

## Score history

- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-07: 72

## 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 468 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 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agproxy.shveik.dev/mcp
- Website: https://agproxy.shveik.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-shveik-agproxy/agproxy.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-shveik-agproxy/agproxy.json
- HTML version of this page: https://verifymcp.io/servers/dev-shveik-agproxy/agproxy