WhoisExtractor MCP
Sign In

Connecting an AI assistant? Start with setup guides →

WhoisExtractor MCP Documentation

Developer documentation for the WhoisExtractor MCP server.

Authentication

Authenticated tools require Authorization: Bearer {token}. Ownership always comes from the token - never pass user_id or customer_id.

During OAuth, sign-in happens on whoisextractor.com/login (magic link, Google, or GitHub). The consent screen appears on the MCP domain after sign-in.

OAuth scopes

Discovery metadata advertises the mcp:use scope. During consent, you grant fine-grained Passport scopes that control which tools your AI can call:

  • account:read - View account information
  • orders:read - View orders and subscriptions
  • downloads:read - View downloads and dataset availability
  • invoices:read - View invoices
  • support:read - View support tickets
  • support:write - Create and reply to support tickets

Write confirmations

Write tools require confirm=false first (preview), then confirm=true with the same idempotency_key.

Discovery endpoints

URLs are generated at runtime from the installed Laravel MCP registrar - do not hardcode paths.

  • MCP server endpoint: https://mcp.whoisextractor.com/mcp
  • OAuth authorization server metadata: https://mcp.whoisextractor.com/.well-known/oauth-authorization-server
  • OAuth protected resource metadata: https://mcp.whoisextractor.com/.well-known/oauth-protected-resource
  • OAuth dynamic client registration: https://mcp.whoisextractor.com/oauth/register
  • OAuth authorization endpoint: unavailable
  • OAuth token endpoint: unavailable

← MCP home