← All updates

Connecting Claude Code (or any MCP client) works again

Starting a connection from Claude Code and then signing up or signing in failed with "Registration failed". The flow now completes, and an expired link says so instead of showing a generic error.

mcpauthfix

Connecting an MCP client — Claude Code, an editor plugin, the CLI's OAuth login — goes authorize → sign in (or create an account) → consent. If you had to sign in or sign up in the middle of that flow, the form came back with a bare "Registration failed", no matter which email or password you used.

The cause was the sign-in link itself, not your details. makesPDF signs the authorization request so it cannot be tampered with, and the auth pages were rewriting that link as they loaded — turning it into a form the signature check no longer recognised. Every attempt from that page failed the same way.

Two things changed. The auth pages now leave a signed link alone, so the flow completes. And when a link really has expired or been altered, the form says so — "This sign-in link has expired or was changed by the browser. Close this tab and start again from the app you were connecting." — instead of a generic failure you cannot act on.

If you hit this: start the connection again from Claude Code (or your client). If a sign-in page has been open for more than ten minutes, reload it first; the signed link is only valid for ten minutes by design.

Alongside the fix, the per-IP limit on creating accounts now actually applies to the endpoint real clients use (five new accounts per hour per address), and a few auth error messages — weak password, malformed email, blocked origin — read as plain English rather than a raw field name.