# Proxygate (remote · gateway.proxygate.ai)

Curated marketplace of real-world data APIs for AI agents, paid per call in USDC on Solana.

- Trust score: 67/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `gateway.proxygate.ai`: 67/100 (this document), [markdown](https://verifymcp.io/servers/ai-proxygate-mcp/gateway.md), [page](https://verifymcp.io/servers/ai-proxygate-mcp/gateway)

## Channel facts

- Endpoint: `https://gateway.proxygate.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1247 tokens (~178/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-proxygate-mcp https://gateway.proxygate.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-proxygate-mcp]
url = "https://gateway.proxygate.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-proxygate-mcp --url https://gateway.proxygate.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-proxygate-mcp:
    url: "https://gateway.proxygate.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-proxygate-mcp": {
      "type": "http",
      "url": "https://gateway.proxygate.ai/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-08-03 (score 67, +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-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

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

### 2026-07-29 (score 63, +1)

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

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (7)

### `browse_apis` (~118 tokens)

Search the Proxygate marketplace for APIs an agent can buy. Optional free-text query (semantic + keyword search, same as the public catalog), category filter, and result limit. Returns each API with its listing id, name, service slug (for call_api), category, buyer price per request (in micro-USDC), listing type, trust/rating hints, and a capped endpoint preview (endpoint_count = full total). No authentication required.

Input parameters:

- `category` (string)
- `limit` (integer)
- `q` (string)

### `get_pricing` (~67 tokens)

Get per-service pricing for Proxygate APIs. Optional single-service filter (exact service slug — take it from browse_apis). Returns the per-request USDC price plus per-input/output token USDC prices (null for per-request services). No authentication required.

Input parameters:

- `service` (string)

### `check_balance` (~58 tokens)

Get the authenticated wallet's Proxygate balance breakdown: total balance, available (spendable now), and pending settlement, all in micro-USDC. Top up via the x402 rail (GET /v1/x402/topup). Requires authentication.

### `get_usage` (~62 tokens)

List the authenticated wallet's recent Proxygate API requests (newest first), with service, path, HTTP status, cost in micro-USDC, and timestamp. Cursor-paginated. Requires authentication.

Input parameters:

- `cursor` (string)
- `limit` (integer)

### `rate_seller` (~80 tokens)

Rate a seller after buying from one of their listings. Give the listing_id and a thumbs verdict (score: true = positive). Proxygate rates the wallet's most recent successful request to that listing (within the last 24h). Rating only, no payment. Requires authentication.

Input parameters:

- `listing_id` (string, required)
- `score` (boolean, required)

### `call_api` (~340 tokens)

Execute a billed API call through Proxygate, end-to-end. Give a listing_id from browse_apis, the endpoint path, and the HTTP method; the service slug is optional (derived from the listing). Optional query/headers/body pass through; set header x-proxygate-shield to off/monitor/strict to control response scanning. Proxygate reserves balance, handles upstream authentication for you, forwards the request, and charges your wallet. Returns the upstream status, headers, and body plus the amount charged (cost_micro_usdc), a signed receipt, and a request_id. Spends from your balance — requires authentication with the mcp:trade (or proxy) scope.

Input parameters:

- `body`: Passthrough request body, upstream-defined JSON value.
- `headers` (object): Allowlisted request headers. Authorization, wallet, and proxy-internal headers are dropped by the gateway.
- `listing_id` (string): Listing id of the seller listing to bill, from browse_apis. Required in practice: calls without it are rejected with guidance (the field stays schema-optional for contract compatibility). service may…
- `method` (string, required): HTTP method for the proxied request. Defaults to GET.
- `path` (string, required): Upstream path with optional inline query string, e.g. "api/v3/simple/price?ids=bitcoin".
- `query` (object): Query parameters as key/value pairs, an alternative to inlining them in path.
- `service` (string): Service slug to call (the proxy path segment). Optional when listing_id is given; the gateway derives it from the listing.

### `describe_endpoint` (~143 tokens)

Inspect one endpoint of a listing before spending: parameters (name, location, required, type), request body schema, and response schemas, resolved one $ref level from the listing's uploaded docs. Give the listing_id from browse_apis plus the endpoint method and path (for GraphQL listings: the operation name as path). No authentication required.

Input parameters:

- `listing_id` (string, required): Listing UUID from browse_apis.
- `method` (string, required): HTTP method of the endpoint, exactly as returned by browse_apis. Ignored for GraphQL listings.
- `path` (string, required): Endpoint path exactly as returned by browse_apis. For GraphQL listings: the operation name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-proxygate-mcp/gateway#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://gateway.proxygate.ai/mcp
- Repository: https://github.com/proxygate-official/proxygate
- Website: https://proxygate.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-proxygate-mcp/gateway/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-proxygate-mcp/gateway/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-proxygate-mcp/gateway