/mcpso/servers/search

POST /api/mcpso/servers/search

Price: 5 credits

Search mcp.so MCP servers by keyword. Returns matching server cards with alias, name, tagline, author, category, star count and the verified/featured flags

How to use it

Keyword lookup over the mcp.so server catalogue. It returns at most 50 servers for any keyword, however many match, and there is no way to page past them — to enumerate a whole segment use /mcpso/servers/browse with a category instead. Pass an `alias` from the result to /mcpso/servers for the overview, install config and tool list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Free-text query matched against server names and taglines (examples: "github", "postgres"; minLength: 1)
• count integer required — Number of servers to return (examples: 20; min: 1; max: 50)

Response

• @type string (default: "McpsoServerCard")
• id string required
• alias string required
• url string required
• name string nullable
• tagline string nullable
• image string nullable
• author_name string nullable
• category_name string nullable
• category_alias string nullable
• star_count integer nullable
• rating number nullable
• rating_count integer nullable
• install_count integer nullable
• status string nullable
• is_remote boolean nullable
• is_verified boolean nullable
• is_featured boolean nullable
• is_editor_pick boolean nullable
• created_at string nullable

Errors

• 422 — 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.