Proxygate
REMOTE · GATEWAY.PROXYGATE.AI · SCANNED AUG 24
Curated marketplace of real-world data APIs for AI agents, paid per call in USDC on Solana.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Proxygate MCP server?
Proxygate is a hosted endpoint at https://gateway.proxygate.ai/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 · gateway.proxygate.ai
claude mcp add --transport http ai-proxygate-mcp 'https://gateway.proxygate.ai/mcp'
{
"mcpServers": {
"ai-proxygate-mcp": {
"url": "https://gateway.proxygate.ai/mcp"
}
}
} {
"servers": {
"ai-proxygate-mcp": {
"type": "http",
"url": "https://gateway.proxygate.ai/mcp"
}
}
} [mcp_servers.ai-proxygate-mcp] url = "https://gateway.proxygate.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-proxygate-mcp": {
"type": "remote",
"url": "https://gateway.proxygate.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-proxygate-mcp --url 'https://gateway.proxygate.ai/mcp' --transport streamable-http
mcp_servers:
ai-proxygate-mcp:
url: "https://gateway.proxygate.ai/mcp" {
"McpServers": {
"ai-proxygate-mcp": {
"Transport": "http",
"Url": "https://gateway.proxygate.ai/mcp"
}
}
} assistant mcp add ai-proxygate-mcp -t streamable-http -u 'https://gateway.proxygate.ai/mcp'
{
"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.
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.
- 24 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Aug 2026 · Probed https://gateway.proxygate.ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of gateway.proxygate.ai. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| gateway.proxygate.ai. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gateway.proxygate.ai/mcp | Unreachable | ||
| http (plaintext) | http://gateway.proxygate.ai/mcp | HTTPS enforced |
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 →
browse_apis ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
call_api ~340
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | HTTP method for the proxied request. Defaults to GET. |
| path | string | yes | 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. |
No output schema declared.
No examples provided.
check_balance ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
describe_endpoint ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | Listing UUID from browse_apis. |
| method | string | yes | HTTP method of the endpoint, exactly as returned by browse_apis. Ignored for GraphQL listings. |
| path | string | yes | Endpoint path exactly as returned by browse_apis. For GraphQL listings: the operation name. |
No output schema declared.
No examples provided.
get_pricing ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | – | – |
No output schema declared.
No examples provided.
get_usage ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
rate_seller ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | – |
| score | boolean | yes | – |
No output schema declared.
No examples provided.
What is the Proxygate MCP server?
Proxygate is an MCP server listed in the public MCP registry as ai.proxygate/mcp. Curated marketplace of real-world data APIs for AI agents, paid per call in USDC on Solana. This page covers its hosted endpoint (https://gateway.proxygate.ai/mcp).
Is the Proxygate MCP server safe to use?
Proxygate scores 0 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 Proxygate MCP server expose?
Proxygate exposes 7 tools: browse_apis, get_pricing, check_balance, get_usage, rate_seller, and 2 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.
Does the Proxygate MCP server require authentication?
Its publisher declares no required credentials for Proxygate. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Proxygate MCP server still maintained?
Proxygate has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 17 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.