POST /api/pulsemcp/servers/search
Price: 10 credits
Search the PulseMCP MCP server directory by keyword, classification and remote availability. Returns server cards with alias, name, provider, description, classification, release date and PulseMCP's estimated weekly visitor count
Omitting `keyword` walks the whole directory, which is what `sort` and `classifications` are for. `classification` is PulseMCP's provenance label — an Anthropic reference implementation, a server published by the vendor of the service it wraps, or a community build — which is the distinction to use when a caller wants vendor-backed integrations only. Pass an `alias` from the result to /pulsemcp/servers for the full profile.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Number of servers to return (examples: 42; min: 1; max: 3360)keyword string nullable — Free-text query matched against server names, providers and descriptions (examples: "github"; minLength: 1)classifications array nullable — Restrict to Anthropic reference servers, official provider servers or community servers; several may be combined (one of: "anthropic-references", "official-providers", "community"; examples: ["official-providers"])remote_only boolean — Return only servers PulseMCP marks as remotely hosted (default: false; examples: true)sort string nullable — Result ordering; omit for PulseMCP's own default order (one of: "recommended", "last-updated-desc", "creation-desc", "alphabetical-asc", "alphabetical-desc", "popular-desc", "popular-total-desc", "popular-30-days-desc"; examples: "creation-desc")@type string (default: "PulsemcpServerCard")alias string requiredurl string requiredname string nullableprovider string nullabledescription string nullableclassification string nullableest_visitor_count_week integer nullablerelease_date 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.