The MCP URL and registered client identifier for an assistant

Describe this account's connector as this deployment would accept it.

Every value is answered by asking the same question the flow itself would ask. The entitlement is the one that is easy to forget and the most confusing to get wrong: /oauth/authorize refuses an account without Remote Link at the consent screen, so a page that printed a URL and a client identifier to such an account would be sending someone to paste two strings and hit entitlement_required with nothing on screen explaining why. Unentitled reads report the refusal and no values.

Deliberately not rate limited, unlike its two neighbours: the /claude page polls it every few seconds for the connection dot, and a budget tight enough to matter here would refuse the page rather than an attacker. It is a session-gated read of rows the caller already owns — a GET /api/nodes with two constants attached — so there is nothing on it worth flooding for. Nothing bounding it is also why what it costs is a property of the route rather than a detail: the entitlement and the node list are two independent questions and are asked at the same time, and the third answer — the deployment's registered client — is the same row for every account here, so it is read from the cached snapshot rather than queried once per poll per open page.