Claude

Connect WhoisExtractor to Claude

MCP supported Recommended setup

Setup information verified September 2026

Official Claude documentation →

Anthropic shows two connector UIs during rollout: newer accounts use Settings → Customize → Connectors; some older accounts use Settings → Capabilities (or Integrations / MCP). Both can add the same remote WhoisExtractor URL. If neither UI offers a custom remote connector, the limit is usually your Claude plan-not WhoisExtractor.

Before you start

  • A WhoisExtractor account (for account, orders, and downloads tools)
  • Claude.ai in a desktop browser (some mobile apps hide connector settings)
  • Custom remote MCP connector support on your Claude plan (Anthropic rollout and plan type vary-see troubleshooting if the menu is missing)

MCP Server URL

Use the same endpoint when connecting Claude, ChatGPT, Cursor or another compatible MCP client.

Setup instructions

  1. 1

    Open Settings

    In claude.ai, open Settings from your profile or account menu.

  2. 2

    Go to Connectors or Capabilities

    New UI: in the left sidebar under Customize, select Connectors. Older UI: open Capabilities, Integrations, or MCP under Settings (Anthropic labels this differently by account). If none of these appear, your plan may not include remote MCP connectors yet.

  3. 3

    Add a custom connector

    New UI: click Add (top right), then choose Add custom connector. Older UI: look for Add connector, Add MCP server, or similar. This adds a remote HTTPS connector-not a chat plugin or file upload.

  4. 4

    Enter name and URL

    Name: whoisextractor (or any label you will recognize). URL: paste the WhoisExtractor MCP endpoint shown on this page (must use https:// and end with /mcp). Click Continue.

  5. 5

    Choose authentication

    Select Required when the server asks. Public catalog tools work without login; account tools prompt you to sign in when needed.

  6. 6

    Choose OAuth client registration

    Select No client ID - register one automatically. WhoisExtractor supports dynamic client registration (DCR).

  7. 7

    Confirm transport (Advanced)

    Expand Advanced → Transport and keep Streamable HTTP selected (the default). Only change this if Anthropic or WhoisExtractor docs instruct otherwise.

  8. 8

    Connect, sign in, and test

    Finish adding the connector. When prompted, sign in at whoisextractor.com/login (magic link, Google, or GitHub), review permissions on the consent screen, then ask Claude: "Show my recent WhoisExtractor orders."

Troubleshooting

I cannot find Connectors, Capabilities, or Add custom connector
Check your Claude plan first-custom remote MCP connectors require eligible subscription and feature access; if the menu is missing entirely, upgrade or ask your org admin (see Anthropic connector docs). Then try both paths: new UI Settings → Customize → Connectors, and older UI Settings → Capabilities or Integrations. Use claude.ai in a desktop browser.
Connector fails to connect
Confirm your Claude plan supports custom remote MCP connectors, the URL uses https:// and ends with /mcp, and transport is set to Streamable HTTP (not SSE).
Wrong authentication mode
Choose Required when the server asks. Always required can work but is unnecessary for public catalog tools.
Authentication error or stale session
Revoke old connections from Dashboard → Settings → Connections, disconnect the connector in Claude, then add it again and complete OAuth.

More troubleshooting →

If your AI app doesn't open after authorization, visit /connected for guidance.

← Back to all AI assistants