# ServerSearcher [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/ServerSearcher/Serversearcher-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/serversearcher

## Description
Search and compare dedicated, VPS, GPU and cloud server plans by specs, location and price.

## Tools
Capabilities this server exposes over MCP:

- **search_servers** — Search the plan catalogue by spec — type (dedicated/virtual/cloud/gpu), min RAM/CPU/disk/bandwidth, GPU model and count, price ceiling, currency, location (ISO country, `COUNTRY-city`, or city id), and provider capabilities (`hasTerraform`, cloud services). Returns plans with on-site URLs and check…
- **get_provider_info** — Provider profile, plan counts, locations and on-site URLs from a provider slug (e.g. `hetzner-cloud`).
- **compare_providers** — Side-by-side comparison of two providers by slug, with the on-site comparison URL.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "serversearcher": {
    "url": "https://www.serversearcher.com/api/mcp"
  }
}
```

## Documentation

## What the ServerSearcher MCP server does

The ServerSearcher MCP server exposes the ServerSearcher catalogue to MCP-compatible AI clients. The catalogue covers dedicated servers, virtual servers, GPU offerings, and cloud plans, including pricing, stock, and location information. Results include links back to the ServerSearcher site and checkout links where available.

Use it to turn infrastructure requirements into a plan search. For example, an agent can look for a dedicated server with at least 64 GB of RAM in Germany and a price below €60. Searches can also include CPU, disk, bandwidth, GPU model, GPU count, currency, and provider capabilities.

## How it works

The service is available at `https://www.serversearcher.com/api/mcp` over streamable HTTP. The `/mcp` path is an alias. Requests use JSON-RPC 2.0 and the MCP `2024-11-05` protocol. The endpoint accepts `POST` requests for MCP operations and supports `GET` and `OPTIONS` as well.

No authentication is required. Clients can discover the service through `/.well-known/mcp.json`, or add the endpoint directly to their MCP configuration. A client can list the available tools and then call a tool with structured arguments such as plan type, minimum specifications, maximum price, and location.

The location filter accepts an ISO country, a `COUNTRY-city` value, or a city ID. Provider capability filters include `hasTerraform` and cloud services. The service applies rate limiting; bursts may receive HTTP `429` responses with a `Retry-After` header.

## Setup and configuration

The ServerSearcher MCP server needs only a streamable HTTP URL in the client configuration. Claude Desktop can use the following entry:

```json
{
  "mcpServers": {
    "serversearcher": {
      "type": "streamable-http",
      "url": "https://www.serversearcher.com/api/mcp"
    }
  }
}
```

Clients that read standard MCP server configurations can use the `/mcp` alias instead. Because the endpoint is public, no API key or environment variable is needed. A basic setup check can call `tools/list` with an HTTP client using JSON content and accept headers.

## Tools and capabilities

- `search_servers` filters the plan catalogue by server type, minimum RAM, CPU, disk, bandwidth, GPU model, GPU count, maximum price, currency, location, and provider capabilities. It returns matching plans with site and checkout links.
- `get_provider_info` accepts a provider slug, such as `hetzner-cloud`, and returns the provider profile, plan counts, available locations, and relevant site URLs.
- `compare_providers` compares two providers by slug and returns a link to the corresponding on-site comparison.

## Limitations and notes

The endpoint is a catalogue search service rather than a provisioning interface. The documented tools provide plan discovery, provider information, and comparison; they do not describe server creation or account management operations. Results are tied to the information available in ServerSearcher’s catalogue, including its live pricing, stock, and location data.

Requests should account for rate limiting. If a burst produces a `429` response, the client should follow the supplied `Retry-After` value before retrying. Provider lookups and comparisons require provider slugs, while location searches must use one of the documented country, country-city, or city-ID formats.

_Full upstream README: https://allmcps.com/mcp/serversearcher/readme_