Proxygate
REMOTE · GATEWAY.PROXYGATE.AI · SCANNED AUG 3
Curated marketplace of real-world data APIs for AI agents, paid per call in USDC on Solana.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · gateway.proxygate.ai
claude mcp add --transport http ai-proxygate-mcp 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": {
"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.
- 3 Aug 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.
- 1 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 2026 · Probed https://gateway.proxygate.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gateway.proxygate.ai | CN=ZeroSSL RSA DV SSL CA 2,O=ZeroSSL GmbH,C=AT | 2 Jul 2026 | 30 Sept 2026 | RSA 2048 | SHA256-RSA | a4425237072ab19dd4d251518182f367 |
| SANs: gateway.proxygate.ai | ||||||
| CN=ZeroSSL RSA DV SSL CA 2,O=ZeroSSL GmbH,C=AT (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 24 Sept 2025 | 23 Sept 2035 | RSA 3072 | SHA384-RSA | d0a908255f8e50e5f3396d1114702a37 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
DNSSEC insecure
Validation of gateway.proxygate.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| proxygate.ai. | 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 | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gateway.proxygate.ai/mcp | Verified | 200 | |
| http (plaintext) | http://gateway.proxygate.ai/mcp | HTTPS enforced | 301 | https://gateway.proxygate.ai:443/mcp |
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.
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.