/smithery/servers

POST /api/smithery/servers

Price: 1 credit

Get one Smithery MCP server by its registry id. Returns the publisher and licence, the repository and homepage links, the hosted MCP endpoint and its last successful deployment, the domain-verification record, the connection config schema, and the full advertised tool, prompt and resource surface with each tool's input schema and behaviour hints.

How to use it

Pass the id exactly as Smithery displays it — `exa` or `owner/name`; an npm-style `@owner/name` is a different string and does not resolve. Reach for this when you need what a server can actually do: `tools` carries every tool's name, description and JSON input schema, which is what you need before wiring a server into an agent, and `config_schema` says which credentials the caller must supply. `mcp_url` is present only for servers Smithery hosts; a listed-only server has a repository and no endpoint. The install count and relevance score that /smithery/servers/search returns are not repeated here. An unknown id comes back as 412, not an empty result.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• server string required — Smithery server id, either a bare name or owner/name, or the address of its Smithery page (examples: "exa", "simosphereai/simosphere-ai", "https://smithery.ai/server/exa"; minLength: 1)

Response

• @type string (default: "SmitheryServerDetail")
• id string required
• url string required
• name string nullable
• namespace string nullable
• alias string nullable
• uuid string nullable
• description string nullable
• homepage string nullable
• icon_url string nullable
• repository_url string nullable
• backlink_url string nullable
• license string nullable
• organization_id string nullable
• mcp_url string nullable
• run_tools_slug string nullable
• created_at string nullable
• last_deployed_at string nullable
• verified boolean nullable
• official boolean nullable
• by_smithery boolean nullable
• remote boolean nullable
• unlisted boolean nullable
• config_allows_empty boolean nullable
• is_secure boolean nullable
• config_schema object nullable
• triggers array (default: [])
• tools array (default: [])
  • @type string (default: "SmitheryTool")
  • name string required
  • display_name string nullable
  • description string nullable
  • task_support string nullable
  • input_schema object nullable
  • output_schema object nullable
  • protocol_meta object nullable
  • annotations object nullable
    • @type string (default: "SmitheryToolAnnotations")
    • display_name string nullable
    • read_only boolean nullable
    • destructive boolean nullable
    • idempotent boolean nullable
    • open_world boolean nullable
• prompts array (default: [])
  • @type string (default: "SmitheryPrompt")
  • name string required
  • description string nullable
  • arguments array (default: [])
• resources array (default: [])
  • @type string (default: "SmitheryResource")
  • uri string required
  • name string nullable
  • display_name string nullable
  • mime_type string nullable
  • description string nullable
• verification object nullable
  • @type string (default: "SmitheryVerification")
  • official boolean nullable
  • homepage_host string nullable
  • verification_value string nullable
  • has_domain_proof boolean nullable
  • has_backlink_proof boolean nullable
  • backlink_url string nullable
  • checked_at string nullable
  • next_check_at string nullable
• deployment object nullable
  • @type string (default: "SmitheryDeployment")
  • deployment_type string nullable
  • mcp_url string nullable
  • upstream_url string nullable
  • config_schema object 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 — No Smithery server carries this id. Confirm it with /smithery/servers/search 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.