Deprecate io.github.perplexityai/mcp-server 0.5.0–0.7.0 — remotes point at mcp.perplexity.ai, which is NXDOMAIN #1575

Title: Deprecate io.github.perplexityai/mcp-server 0.5.0–0.7.0 — remotes point at mcp.perplexity.ai, which is NXDOMAIN

Repo: modelcontextprotocol/registry

Server

io.github.perplexityai/mcp-server

Not the publisher — reporting this as a consumer who hit the dead endpoint. The publisher has already fixed it going forward; only the historical records are stale.

Current state

Seven versions are returned with status: active and a remotes entry pointing at a hostname that does not resolve:

$ curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.perplexityai"

io.github.perplexityai/mcp-server v0.5.0  status=active  remote=https://mcp.perplexity.ai/mcp
io.github.perplexityai/mcp-server v0.5.1  status=active  remote=https://mcp.perplexity.ai/mcp
io.github.perplexityai/mcp-server v0.5.2  status=active  remote=https://mcp.perplexity.ai/mcp
io.github.perplexityai/mcp-server v0.6.0  status=active  remote=https://mcp.perplexity.ai/mcp
io.github.perplexityai/mcp-server v0.6.1  status=active  remote=https://mcp.perplexity.ai/mcp
io.github.perplexityai/mcp-server v0.6.2  status=active  remote=https://mcp.perplexity.ai/mcp
io.github.perplexityai/mcp-server v0.7.0  status=active  remote=https://mcp.perplexity.ai/mcp

v0.7.1 (isLatest: true for this namespace) has no remotes block — the publisher dropped it — but the seven earlier records remain active and resolvable.

The host does not exist

Confirmed on three independent public resolvers:

@8.8.8.8   status: NXDOMAIN   answer: empty
@1.1.1.1   status: NXDOMAIN   answer: empty
@9.9.9.9   status: NXDOMAIN   answer: empty

$ curl -sS --max-time 10 https://mcp.perplexity.ai/mcp
curl: (6) Could not resolve host: mcp.perplexity.ai

Two controls, to rule out the alternatives:

# sibling host resolves on the same resolvers -> not a resolver fault
$ dig @8.8.8.8 +short api.perplexity.ai
104.18.27.48

# parent zone is live and authoritative -> not a domain-wide outage
$ dig @8.8.8.8 +short perplexity.ai SOA
emerson.ns.cloudflare.com. dns.cloudflare.com. 2413160383 10000 2400 604800 1800

Requested action

Set versions 0.5.0 through 0.7.0 of io.github.perplexityai/mcp-server to deprecated (or deleted, if that is the preferred retirement policy for records advertising an unreachable endpoint), with a status message along the lines of:

Hosted remote mcp.perplexity.ai has been retired and no longer resolves. Use the maintained server at ai.perplexity/mcp-server, or the documented hosted endpoint https://api.perplexity.ai/mcp.

Context

• Active development moved to the namespace ai.perplexity/mcp-server (latest 1.2.0, published 2026-07-27). No version under that namespace declares a remotes block.
• The publisher's README documents https://api.perplexity.ai/mcp as the hosted endpoint. I verified it returns HTTP 200 to an authenticated initialize, so a working replacement exists.
• The stale entry originates in server.json at v0.5.2 (commit ac919f05), which declared "url": "https://mcp.perplexity.ai/mcp". Current main no longer contains it.
• A client resolving this server by name and version gets the dead remote and fails with a DNS error that points nowhere near the real cause. The README is correct, but a client resolving through the registry never reads it.

Filed in parallel with the publisher at perplexityai/modelcontextprotocol, since they own the namespace and can publish a deprecation update directly.