EscortFox

npx add-mcp 'https://escortfox.com/mcp'

Developers

Read-only EscortFox API, remote MCP server, A2A agent and WebMCP tools: countries, cities, districts, services and listing summaries, no API key needed.

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

EscortFox offers read-only access to its directory for AI assistants, developer tools and partner widgets that point people to escortfox.com. There are four ways in, all backed by the same data and the same terms: a REST API, a remote MCP server, an A2A agent, and WebMCP tools on the website itself. None of them needs an API key or an account.

What you get, and what you don't

Every listing comes back as a summary: name, city and district, age, a price-from, a short teaser, one small preview image and the listing's URL on escortfox.com. Contact details, full descriptions, galleries and reviews are only on the website: follow the url.

Documentation

• Public API: the REST endpoints, their parameters and an example request.
• Limits and terms of use: rate limits, caching, attribution and what is not allowed.
• MCP server: a remote Model Context Protocol server with six read-only tools.
• A2A agent: the same tools for clients of the Agent2Agent protocol.
• WebMCP: the same tools, registered by every page of escortfox.com in the visitor's browser.

For AI agents

Every page of these docs is also available as Markdown: add .md to its URL (for example /developers/api.md) or request the page with Accept: text/markdown. All of them are listed in /developers/llms.txt. A short, curated summary of the whole site, with its URL scheme and main pages, is at /llms.txt.

Contact

Questions or a problem with the API or the MCP server: e-mail info@escortfox.com. To report a security issue, see the vulnerability disclosure policy.