R/RegistryReady

REMOTE MCP SERVER.JSON

Describe the endpoint,
not the credential.

Remote registry entries should expose a reachable HTTPS URL and declare required headers or URL variables without embedding private values.

Check remote metadata →

Remote metadata essentials

01

HTTPS URL

Publish a stable public endpoint. Localhost and private network addresses cannot be used by registry consumers.

02

Transport

Prefer streamable HTTP for current remote MCP servers. Treat legacy SSE configurations as migration candidates.

03

Secret inputs

Describe authorization headers as secret variables. Never place a bearer token directly in server.json.