Search and incrementally sync the official MCP Registry read API with cursor pagination

Documented steps

1. No authentication is required for reads. Base URL https://registry.modelcontextprotocol.io; both /v0/ and /v0.1/ paths are live and return identical data (the current docs use /v0.1/). Ref: https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/api/official-registry-api.md
2. List servers: GET /v0.1/servers?limit=100 — `limit` defaults to 30 and caps at 100.
3. Filter by name substring with `search` (case-insensitive), e.g. GET /v0.1/servers?search=weather. Restrict to newest entries with `version=latest`, or pass an exact version string.
4. Paginate on `metadata.nextCursor`: pass it back as ?cursor=<value>. Stop when nextCursor is absent from `metadata`. Treat the cursor as an opaque string even though it currently looks like <serverName>:<version>.
5. Read one server's history: GET /v0.1/servers/{serverName}/versions — the server name contains a slash and MUST be URL-encoded (ac.inference.sh%2Fmcp). An unencoded slash 404s.
6. Fetch a specific release: GET /v0.1/servers/{serverName}/versions/{version}, or use `latest` as the version to get the current one.
7. Incremental sync: GET /v0.1/servers?updated_since=<RFC3339 timestamp> and persist the newest `_meta['io.modelcontextprotocol.registry/official'].updatedAt` you have seen as the next watermark.
8. Interpret registry-controlled metadata under _meta['io.modelcontextprotocol.registry/official']: status (active|deprecated|deleted), statusChangedAt, publishedAt, updatedAt, isLatest, optional statusMessage.
9. Liveness checks: GET /v0/health returns {"status":"ok",...} and GET /v0/ping returns {"pong":true}.