/pulsemcp/servers/manifests

POST /api/pulsemcp/servers/manifests

Price: 1 credit

Return the community-standard server.json manifest for one PulseMCP server, one row per published version newest first: package identifiers and registries, transports, runtime hints, declared arguments and environment variables, remote endpoints, icons, repository and website

How to use it

This is the machine-readable install descriptor an MCP client consumes, so it is the right endpoint when the caller wants to actually run a server rather than read about one. `packages` and `remotes` are passed through exactly as published, so they can be handed to an installer unchanged. PulseMCP keeps every past version, so raise `count` only when the history matters — otherwise the first row is the current manifest. An empty result means the server has no published manifest, not that the server is missing.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• server string required — PulseMCP server alias, or the full server URL (examples: "modelcontextprotocol-filesystem", "https://www.pulsemcp.com/servers/github"; minLength: 1)
• count integer required — Number of manifest versions to return (examples: 10; min: 1)

Response

• @type string (default: "PulsemcpServerManifest")
• alias string required
• url string required
• version string nullable
• version_index integer nullable
• ingested_at string nullable
• name string nullable
• display_name string nullable
• description string nullable
• website_url string nullable
• schema_url string nullable
• repository object nullable
• packages array (default: [])
• remotes array (default: [])
• icons array (default: [])

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.