# Wondel.ai MCPs auth.md You are an agent. This file tells you how to authenticate to the 26 remote MCP servers on `https://mcp.wondel.ai`. The short version: you don't. Every server is public and anonymous, so the usual sequence (discover, register, claim, exchange, use, handle revocation) collapses to one step: connect and call. ```yaml service: Wondel.ai MCP servers audience: AI agents and MCP clients acting for a person authentication: none methods_supported: [anonymous] registration: not required, not offered credentials: none issued, none accepted oauth_metadata: none (no /.well-known/oauth-protected-resource, no /.well-known/oauth-authorization-server) transport: Streamable HTTP at https://mcp.wondel.ai//mcp terms: https://mcp.wondel.ai/legal.txt contact: support@wondel.ai ``` ## Who this is for An agent (Claude Code, Cursor, a custom MCP client, an orchestrator) that wants live data from a public site or official API through one of these servers, on behalf of one person asking one question. Everything here is read-only public data; nothing is tied to a user identity, so there is no identity to assert. ## Step 1: Discover There is no OAuth discovery to run and no 401 that points you anywhere. What exists instead: - `https://mcp.wondel.ai/.well-known/mcp/server-card.json`: the MCP Server Card for the host. - `https://mcp.wondel.ai/catalog.json`: every server with its `id`, category, summary, latency and status. Skip entries whose status is `disabled`: those are withdrawn. - `https://mcp.wondel.ai/llms.txt`: the same list for reading, with the legal notice. - `https://mcp.wondel.ai/mcp`: a directory MCP server whose one tool, `list_servers`, returns each server's endpoint, status and tool names. Pick a server `` from any of these. ## Step 2: Register Skip this step. There is no account, signup form, API key, client registration or claim ceremony, and nothing to ask the user to approve. An agent is ready the moment it reads this file. ## Step 3: Authenticate The only supported method is **anonymous**. A plain MCP `initialize` over Streamable HTTP is the whole handshake: ```http POST https://mcp.wondel.ai//mcp Content-Type: application/json Accept: application/json, text/event-stream ``` Send no `Authorization` header, no `X-API-Key`, no cookie, no client certificate. A header you add is ignored by the service and only leaks whatever it contains into a request to a third party. If your client requires a credential field to be non-empty, leave it blank or remove the server's auth block. Not supported: OAuth 2.0 of any flavour, API keys, bearer tokens, basic auth, identity assertions, mTLS. ## Step 4: Use credentials There are none. Nothing to store, scope, refresh, rotate or revoke, and no token expiry to handle. Treat every connection as fresh and stateless; the servers keep no sessions and no user accounts. ## Step 5: Call ```bash claude mcp add --transport http otodom https://mcp.wondel.ai/otodom/mcp ``` or, in any MCP client's servers config, a bare URL: `https://mcp.wondel.ai/otodom/mcp`. Then call the server's tools. Replace `otodom` with the `` you picked. Responses to expect that are not authentication problems: - A tool failure arrives inside an HTTP 200 MCP result with `isError: true` and an `Error:` text. When the call itself is at fault, the text names the parameter or value to change and ends with a link to `https://mcps.wondel.ai/servers//`: fix the input, because no credential would have changed the outcome. A provider outage reads as a plain `Error:` with nothing to fix: wait and retry once, later. - `https://mcp.wondel.ai//sse` answers HTTP 410: the 2024 HTTP+SSE transport is retired. Use `//mcp`. - A withdrawn server answers HTTP 451 and disappears from every catalog except `catalog.json`, where it stays marked `status: "disabled"`: its operator asked for it to be taken down. ## Fair use instead of quotas No account means no per-account quota. The limits that exist belong to the sites and paid providers behind the servers and are shared by every caller. Keep to one query per user question, let slow servers finish (the catalog states each server's latency), and do not loop over dates, pages or cities or fan out hundreds of calls. Bulk querying that rebuilds a source's data is forbidden by the terms and may get a caller blocked. ## Legal notice - Unofficial, experimental servers run by Wondel.ai, free of charge; not affiliated with or endorsed by any source site. - Data is fetched on demand from third-party sites and official APIs. Copyright, database rights and trademarks stay with the source operators; nothing here grants a licence. - Intended for personal use (looking something up for yourself through an assistant), plus testing, research and demonstration of MCP integrations. Not for bulk querying, redistribution, competing databases or training datasets. - Attribute results to their source and keep the original links. Data may be stale or wrong; verify at the source before deciding. Provided as-is, without warranty. - Rights holders and site operators: write to support@wondel.ai and the server is withdrawn promptly (it then answers HTTP 451). The same address takes reports of inaccurate data and personal-data removal requests. - Full terms, Polish binding with an English translation: https://mcp.wondel.ai/legal.txt ## Contact Questions about access, a report of wrong data, a personal-data removal request, or a takedown notice from a rights holder: support@wondel.ai. Terms: https://mcp.wondel.ai/legal.txt. Human docs for every server: https://mcps.wondel.ai.