One tool that answers questions about Escape's public API, grounded in the live OpenAPI spec rather than a snapshot.
LABSCO SUMMARY
An OpenAPI spec is the one artefact that cannot drift from the implementation without something breaking, so answering from it rather than from prose is the strongest form this kind of tool takes. One tool, no ambiguity about which to call, and nothing about your account is reachable. The rotation behaviour is worth knowing operationally: rotating a key forces every connected client through consent again, which is correct and disruptive.
Escape's endpoint, with a single tool. It is a documentation server for their public API, and its answers are grounded in the OpenAPI specification as it currently stands.
public_api_answer_question — any question about the Escape public API, answered against the live spec.
OAuth 2.1 with PKCE following the current MCP authorisation spec, or a static key header. Registration is a no-op returning a shared public client id. Key rotation invalidates cached clients and forces re-consent.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
Ask about the endpoint and have it answered from the live OpenAPI spec.
Keep the documentation reachable in the editor instead of a browser tab.
Listed in project docs. Your client may show a different list.
public_api_answer_questionGrounds any question about the Escape Public API in the live OpenAPI spec at https://public.escape.tech/v3/openapi.json and returns a copy-pasteable cURL example; returns best-matching operation (up to 3 with limit); never echoes the caller's real API key ($ESCAPE_API_KEY placeholder)
BEFORE YOU INSTALL
1 tool named in the project's documentation.
INSTALLATION
Add the endpoint to your client, then approve the OAuth consent screen.
https://mcp.escape.tech/mcpMCP servers
yWorks
ref-tools
VIKAS9793