Troubleshooting
Before contacting support
- ✓ URL ends with /mcp
- ✓ HTTPS works in production (http only for local .test domains)
- ✓ AI client supports remote MCP
- ✓ WhoisExtractor account is active
- ✓ OAuth completed successfully
- ✓ Connection has not been revoked
- ✓ Your AI plan supports required MCP capability
- ✓ MCP is enabled (MCP_ENABLED=true)
Test with MCP Inspector first
Before debugging Claude, ChatGPT, or Cursor, verify the server with the official MCP Inspector:
npx @modelcontextprotocol/inspector@v1-latest \ --transport http \ --server-url https://mcp.whoisextractor.com/mcp
When OAuth opens a browser, sign in at whoisextractor.com/login (magic link, Google, or GitHub).
My AI cannot connect
Verify the MCP URL, client MCP support, and that https://mcp.whoisextractor.com/mcp is reachable.
OAuth keeps looping
Clear cookies for the MCP domain and retry. Ensure you complete sign-in at whoisextractor.com/login.
No tools appear
Confirm OAuth completed and scopes were granted. Revoke and reconnect if needed.
Authentication fails
Check account status and revoke stale connections from Dashboard → Settings → Connections.
I revoked access
Create a new connection from your AI client setup guide.
Write actions unavailable
Ensure you opted in to support actions during consent and your AI client allows write tools.
Server unavailable
Verify MCP is enabled and the endpoint uses HTTPS in production.
Discovery metadata errors
Check /.well-known/oauth-authorization-server returns JSON with authorization and token endpoints.
MCP Server URL