POST /api/mcpso/servers/remote
Price: 1 credit
Walk mcp.so's catalogue of hosted MCP servers — the ones reachable over a URL instead of being run locally — optionally restricted to one category or to featured or verified entries
Use this when the caller needs servers they can connect to without installing anything locally. It is a separate, much smaller catalogue than /mcpso/servers/browse, and its entries carry the same aliases, so an `alias` from here resolves at /mcpso/servers. The `reasoning` category exists on the main catalogue but holds no remote servers, which is why it is not offered here.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Number of remote servers to return (examples: 60; min: 1)category string nullable — Restrict to one mcp.so category (one of: "ai-agents", "memory-knowledge", "search", "browser-automation", "data-analytics", "developer-tools", "version-control", "productivity", "databases", "cloud-infra", "files-storage", "communication", "media-design", "finance-commerce", "other"; examples: "search")tag string nullable — Restrict to editorially featured or verified servers (one of: "featured", "verified"; examples: "verified")sort string nullable — Order by newest addition or by name; omit for the site's own default order (one of: "latest", "name"; examples: "latest")@type string (default: "McpsoServerCard")id string requiredalias string requiredurl string requiredname string nullabletagline string nullableimage string nullableauthor_name string nullablecategory_name string nullablecategory_alias string nullablestar_count integer nullablerating number nullablerating_count integer nullableinstall_count integer nullablestatus string nullableis_remote boolean nullableis_verified boolean nullableis_featured boolean nullableis_editor_pick boolean nullablecreated_at string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.