# RMCP API

No authentication is required. Prefer stable `/api/v1` routes. Results are paginated with `limit` (maximum 100) and `offset`, rate limited, and return structured errors. Server searches accept `sort` — `relevance` (default with a query), `a-z` (default without one), `z-a`, `newest`, `oldest`, `tools` or `endpoints` — and echo the applied value.

- `GET /api/v1/servers/search?q=payments&limit=20&offset=0&sort=relevance`
- `GET /api/v1/tools/search?q=website+technology&authentication=none`
- `GET /api/v1/servers/{id}`
- `GET /api/v1/tools/{id}`
- `GET /api/v1/servers/{id}/install?client=codex`
- `GET /api/v1/servers/{id}/trust`
- `GET /api/v1/servers/{id}/status`
- `GET /api/v1/servers/compare?ids=id1,id2`
- `POST /mcp` — MCP Streamable HTTP JSON-RPC

Trust responses contain normalized evidence and upstream data, never credentials. Endpoint status is retrieved only for indexed records; the public discovery API does not probe arbitrary URLs. See `/openapi.json` for the machine-readable definition.