# MCP server

> The EscortFox remote MCP server at https://escortfox.com/mcp: Streamable HTTP, no sign-in, six read-only tools over the Public API.

Source: https://escortfox.com/developers/mcp. Index of all EscortFox developer docs: https://escortfox.com/developers/llms.txt

A remote [Model Context Protocol](https://modelcontextprotocol.io) server at `https://escortfox.com/mcp` (Streamable HTTP, stateless, no sign-in). It exposes six read-only tools over the [Public API](https://escortfox.com/developers/api.md).

## Tools

- `search_listings`: Search escort, venue or agency listings in a city, with district, service and verified filters.
- `get_listing`: One listing summary by id.
- `list_countries`: Countries with active listings.
- `list_cities`: Cities of a country.
- `list_districts`: Districts of a city.
- `list_services`: The service vocabulary.

## Configuration

Not a developer? The step-by-step guide [Search EscortFox from your AI assistant](https://escortfox.com/guide/search-escorts-with-ai-assistant) shows how to add it in Grok, ChatGPT and Perplexity.

Add it to any MCP client that supports remote servers by its URL. In a JSON configuration that takes remote servers:

```json
{
  "mcpServers": {
    "escortfox": { "url": "https://escortfox.com/mcp" }
  }
}
```

## Discovery

The server card is at [/.well-known/mcp.json](https://escortfox.com/.well-known/mcp.json), and the server is listed in the official MCP Registry as `com.escortfox/escortfox`. The API [limits](https://escortfox.com/developers/limits.md) apply per calling address, with a larger allowance for AI assistants that call from their providers' published ranges, and tool results include the listing URL on escortfox.com.