Skip to main content

Troubleshooting

Sign-in ends with access_denied​

The authorization server refused the request, usually because of the scopes the client asked for.

  • NameBeta grants only the identity scopes profile and email. There is no API scope, and a client configured to request one — mcp:tools, for instance — can be refused. Remove any custom scope setting from the client so that it uses the scopes the server advertises.
  • You clicked Cancel on the consent screen. Start the connection again and approve access.

Requests fail with invalid_token​

The client sent a token the server does not accept. The 401 response carries WWW-Authenticate: Bearer … error="invalid_token".

  • The token expired. Clients normally refresh or re-authorize on their own. If yours does not, disconnect and connect again.
  • The token was issued for another resource. Tokens must have the audience https://namebeta.com/api/mcp. Check that the client sends resource=https://namebeta.com/api/mcp in the authorization request, and that the server URL in the client is exactly https://namebeta.com/api/mcp — no trailing slash, no www.
  • A token was pasted into the configuration. Remove any Authorization header or bearer token from the client configuration and let it sign in through OAuth.

The client keeps asking me to sign in​

  • Make sure the sign-in completes: after approving access, wait until the browser says you can return to the app. Closing the tab early leaves the client without a token.
  • Browser extensions that block pop-ups or third-party redirects can break the return to the client. Try again in a private window, or allow redirects for auth.namebeta.com.
  • Remove the server from the client and add it again. This clears a stored token that no longer works.

"Does not support dynamic client registration"​

Your client can only register itself through Dynamic Client Registration (DCR), which NameBeta does not offer. Update the client — most current clients support Client ID Metadata Documents — or ask for a pre-registered client ID; see Other clients.

Calls fail with 429 or "quota exceeded"​

You have used up an hourly or daily limit of your plan. The Retry-After header and error.data.retryAfter say how many seconds remain until the limit resets.

  • Hourly limits reset at the start of each UTC hour, daily limits at 00:00 UTC — not at midnight in your time zone.
  • The allowance is shared with the website: lookups you make on namebeta.com while signed in come out of the same buckets.
  • Other tools use other buckets and keep working.
  • Check your current usage on the usage page of your account panel, and see Quotas and errors for the limits of each plan.

A tool is missing, or "Tool … not found"​

NameBeta has five tools: check_availability, compare_prices, suggest_domains, lookup_whois and lookup_dns.

  • If the client lists fewer, you may have switched some off in its settings (ChatGPT and Cursor let you do this per tool).
  • If a call fails with Tool … not found, the client is using a cached tool list or a name from an older version of the server. Refresh the server's tools in the client, or reconnect.

The wrong NameBeta account is connected​

Calls count against the account you signed in with during authorization. To switch, disconnect the server in the client (in Claude Code, clear its authentication under /mcp), sign out at namebeta.com, and connect again.

A result looks wrong​

Results come from live registry, WHOIS and DNS queries at the moment of the call. An unknown status or a failed lookup usually means an upstream server did not answer in time; try again a little later. Confirm availability and price with the registrar before you register.

Still stuck?​

Write to contact@namebeta.com with the client you use, the time of the failure in UTC, and the error message. The MCP server comes without an SLA, so we cannot promise a response time.

Last updated on