mcp server
Proxygate
Curated marketplace of real-world data APIs for AI agents, paid per call in USDC on Solana.
Description as published by the maintainer. Source
- version 1.0.1
- active
active — Most recent push to the repository was 2026-06-23.
What this server can do
7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
browse_apis(q, limit, category)- 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.
call_api(body, path, query, method, headers, service, listing_id)- 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. Required: path, method.
check_balance- 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.
describe_endpoint(path, method, listing_id)- 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. Required: listing_id, method, path.
get_pricing(service)- 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.
get_usage(limit, cursor)- 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.
rate_seller(score, listing_id)- 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. Required: listing_id, score.
Last successful function declaration observed on . Source: https://gateway.proxygate.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://gateway.proxygate.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 4 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-06-23 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-25 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-25 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 7 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | gateway.proxygate.ai | |
| mcp endpoint status | ok | The server listed 7 functions when asked. | as of probe | gateway.proxygate.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json