If your runtime supports remote MCP, point it here:
- Endpoint —
https://mcp.index.webenta.sk/mcp - Transport — Streamable HTTP (preferred) or SSE.
- Auth —
Authorization: Bearer <api-key>header, or OAuth 2.1 with client id (any string) and client secret (= API key).
#Discovery
Tools, prompts and resource templates are advertised via the standard MCP capability handshake. No bespoke setup beyond auth.
OAuth discovery
OAuth metadata is served at the same origin under
/.well-known/oauth-authorization-server, so spec-compliant clients can fully self-configure.