/pulsemcp/servers

POST /api/pulsemcp/servers

Price: 1 credit

Get one PulseMCP MCP server profile: provider, classification, description, release date, GitHub repository and stars, PulseMCP's estimated visitor counts and global popularity ranking, the server.json identifier, and any published use cases

How to use it

Resolves one server from its PulseMCP alias or any pulsemcp.com/servers URL. `popularity_rank` and `est_visitor_count` are PulseMCP's own estimate of usage across the whole MCP ecosystem, not a download count from any one registry, and the site publishes them rounded, so treat both as approximate. `remotes` is what tells you the server can be reached over a URL without installing anything; it is empty for the ordinary locally-run server. For the machine-readable install manifest call /pulsemcp/servers/manifests with the same alias.

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)

Response

• @type string (default: "PulsemcpServer")
• alias string required
• url string required
• name string nullable
• provider string nullable
• provider_url string nullable
• classification string nullable
• description string nullable
• est_visitor_count integer nullable
• est_visitor_count_week integer nullable
• popularity_rank integer nullable
• popularity_rank_week integer nullable
• release_date string nullable
• github_url string nullable
• github_star_count integer nullable
• marketing_url string nullable
• server_json_url string nullable
• server_json_name string nullable
• maintainer_note string nullable
• is_top_pick boolean (default: false)
• remotes array (default: [])
  • @type string (default: "PulsemcpServerRemote")
  • url string required
  • name string nullable
  • transport string nullable
  • auth_type string nullable
  • cost string nullable
• use_cases array (default: [])
  • @type string (default: "PulsemcpUseCase")
  • name string required
  • url string required
  • category string nullable
  • description string nullable
  • author_name string nullable
  • client_name 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 — Server not found 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.