EscortFox
REMOTE · ESCORTFOX.COM
Read-only search of the EscortFox escort directory: cities, services and listing summaries.
Available components
Last scanned (5 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 981 tokens (~163/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://escortfox.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=escortfox.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | abccd261fac9183313a2ee6202338536 |
| SANs: escortfox.com, *.escortfox.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of escortfox.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| escortfox.com. | DS published | 2371 | 13 | Verified |
| escortfox.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://escortfox.com/mcp | Verified | 200 | |
| http (plaintext) | http://escortfox.com/mcp | HTTPS enforced | 301 | https://escortfox.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_listing Get a listing ~102
Get the summary of one EscortFox listing by its numeric id — the number at the end of a listing link (…/anna-12345 → 12345). Returns the same fields as search_listings and the listing's escortfox.com link; contact details and photos are only on that page.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The listing id. |
| lang | string | – | Language of the teaser text and of the escortfox.com links. Default "en". |
No output schema declared.
No examples provided.
list_cities List cities ~136
List the cities of a country that have active listings, busiest first, with escort and venue counts and each city's escortfox.com link. Use the city slug as `city` in search_listings, and the city's region as `country` where it differs from the country code (US states, e.g. "US-CA").
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Required. ISO 3166-1 alpha-2 country code (e.g. "DE"), or a city's region code where the site splits a country by state (e.g. "US-CA"). Get valid values from list_countries / list_cities. |
No output schema declared.
No examples provided.
list_countries List countries ~47
List the countries that have active EscortFox listings, with the number of escort and venue listings in each. Use a country code as `country` in list_cities and search_listings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_districts List districts ~124
List the districts of a city that have active listings (most cities have none). Use a district slug as `district` in search_listings.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Required. City slug from list_cities. |
| country | string | yes | Required. The city's region from list_cities, or its ISO 3166-1 alpha-2 country code (e.g. "DE"), or a city's region code where the site splits a country by state (e.g. "US-CA"). Get valid values fro… |
No output schema declared.
No examples provided.
list_services List services ~37
List the service vocabulary of escort listings (slug and English name). Use a slug as `service` in search_listings (escort searches only).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_listings Search listings ~377
Search the EscortFox directory of independent escorts, agencies and venues in one place. Returns up to 20 listing summaries per page: name, location, age, starting rate, verification status, incall/outcall, venue type, a short teaser and the listing's escortfox.com link. Summaries have no contact details or photos: always give the user each listing's link, where both are shown. "escort" and "venue" searches need country + city (find them with list_countries and list_cities); "agency" searches need country only. Only pages 0-4 (100 results) exist — narrow the search with district, service or verified instead of paging further.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City slug from list_cities (e.g. "berlin"). Required for escort and venue searches; not allowed for agency searches. |
| country | string | yes | Required. ISO 3166-1 alpha-2 country code (e.g. "DE"), or a city's region code where the site splits a country by state (e.g. "US-CA"). Get valid values from list_countries / list_cities. |
| cursor | string | – | For the next 20 results: the `nextCursor` of the previous search_listings result, unchanged. Omit for the first page. |
| district | string | – | Optional district slug from list_districts (escort and venue searches). |
| lang | string | – | Language of the teaser text and of the escortfox.com links. Default "en". |
| service | string | – | Optional service slug from list_services (escort searches only). |
| type | string | yes | What to search: "escort", "venue" or "agency". |
| verified | boolean | – | true = only escorts whose photos and phone are verified (escort searches only). |
No output schema declared.
No examples provided.
How do I install the EscortFox MCP server?
EscortFox is a hosted endpoint at https://escortfox.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · escortfox.com
claude mcp add --transport http com-escortfox-escortfox 'https://escortfox.com/mcp'
What is the EscortFox MCP server?
EscortFox is an MCP server listed in the public MCP registry as com.escortfox/escortfox. Read-only search of the EscortFox escort directory: cities, services and listing summaries. This page covers its hosted endpoint (https://escortfox.com/mcp).
Is the EscortFox MCP server safe to use?
EscortFox scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EscortFox MCP server expose?
EscortFox exposes 6 tools: search_listings, get_listing, list_countries, list_cities, list_districts, list_services. Their descriptions and schemas cost roughly 823 tokens of context every time the server is loaded.
Does the EscortFox MCP server require authentication?
No. We connected to EscortFox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EscortFox MCP server still maintained?
EscortFox is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EscortFox MCP server?
VerifyMCP ran 13 checks on EscortFox, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.