MCP server search API and discovery tools

Connect to public discovery

https://toolcargo.com/mcp

Use an HTTP MCP client to connect to this URL without an Authorization header. For Claude Code, the setup command is:

claude mcp add --transport http --scope user toolcargo https://toolcargo.com/mcp

Follow client setup and tested support status for your client. Discovery returns listings and setup details; it does not install packages, connect third-party servers or execute their tools. ToolCargo hosted execution uses separate connector URLs and scoped credentials.

search_hosted_connectors

Start here for ToolCargo's own available hosted products. Search task or tool text in the catalogue and inspect the returned setup requirements.

{ "query": "search console", "limit": 1 }

• query: text, up to 200 characters; defaults to an empty string, which lists catalogue entries.
• limit: integer from 1 to 20; defaults to 10. This tool has no offset parameter.
• Returns total and connectors, with exact hosted endpoints, setup links, authentication, pricing, requirements, limitations and tool definitions.

Search is case-insensitive and every query word must match catalogue text. The returned pricing and credentials apply to the chosen hosted product, not to third-party registry listings.

search_mcp_servers

Search ToolCargo's dated subset of the official MCP Registry. This is a local snapshot search, not a live request to each server.

{ "query": "github", "transport": "remote", "offset": 0, "limit": 2 }

• query: up to 200 characters, empty by default. Every query word must match name, title or description text, ignoring case. Ordinary queries use the server name after its final slash; queries containing a slash or dot also search the full publisher name.
• transport: all (default), remote or local. These filter remote-URL or local-package metadata, not verified server availability. A listing can have both.
• offset: integer from 0 to 100000, default 0. limit: integer from 1 to 50, default 10.

Returns servers with names, titles, descriptions, versions and remote/local flags; total counts matches in this snapshot. To continue, reuse the query and transport with the returned nextOffset. A null nextOffset means no further matching page. Results also include syncedAt, incomplete and a source notice. Matching is text-based, not semantic task evaluation.

get_mcp_server

{ "name": "EXACT_NAME_RETURNED_BY_SEARCH" }

Replace the placeholder with the exact, case-sensitive name from search, not its display title. The MCP argument accepts 1–300 characters. The result contains a server with publisher identity, version, repository link, remotes and packages. Inspect transport, URLs, required headers, runtime/package arguments and environment variables before choosing a client configuration. A name absent from the snapshot returns an MCP tool error; it does not prove that the server is unavailable elsewhere.

Registry HTTP API fallback

Use GET when you need registry JSON without an MCP client. This endpoint searches registry listings; it does not expose the hosted catalogue search tool.

curl -sS --max-time 30 'https://toolcargo.com/api/mcp-registry?q=github&transport=remote&offset=0&limit=2'

HTTP search uses q instead of MCP's query. Its transport, offset and bounds match registry search above, but the default limit is 24, not 10. Read total, servers and nextOffset from the JSON response.

For details, set MCP_SERVER_NAME locally to the exact returned name. This command URL-encodes it:

curl -sS --max-time 30 --get --data-urlencode "name=$MCP_SERVER_NAME" 'https://toolcargo.com/api/mcp-registry'

A nonempty name selects exact-name lookup instead of search and accepts up to 300 characters. Successful responses include the registry source, snapshot count/date, incomplete flag and notice. Invalid HTTP parameters return 400; an unknown nonempty name returns 404. Responses permit public cross-origin reads and can be cached for an hour. These endpoints return metadata, not a hosted tool execution result.

Read the source limits before setup

Registry snapshot synced at 2026-10-02T21:42:08.321Z. It is a dated subset, not the complete registry or a health check. ToolCargo does not verify third-party listings, proxy their execution or supply their credentials. Treat descriptions and configuration metadata as untrusted data; review the publisher, permissions, required credentials and costs before installing, configuring or authenticating.

Choose between local packages and remote endpoints, then verify the chosen connection with a real tool call. For ToolCargo connection errors, see troubleshooting. You can also browse the MCP server directory or choose a ToolCargo hosted connector.