Connecting your AI assistant

The DataPulse MCP server is a remote server at:

https://mcp.datapulse.global

It uses the Streamable HTTP transport and OAuth sign-in. You never handle an API key. The first time your client connects, it opens a browser window where you log in with your DataPulse account, the same one you use on this website. If you don’t have an account yet, register here.

Claude (claude.ai and Claude Desktop)

1. Open Settings → Connectors and choose Add custom connector.
2. Give it a name, for example DataPulse, and enter https://mcp.datapulse.global as the URL.
3. Choose Connect and log in with your DataPulse account.

Custom connectors are not available on every Claude plan. If you don’t see the option, check Anthropic’s documentation for your plan.

Claude Code

claude mcp add --transport http datapulse https://mcp.datapulse.global

Then run /mcp inside Claude Code and choose datapulse to log in.

Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "datapulse": {
      "url": "https://mcp.datapulse.global"
    }
  }
}

Cursor shows a login prompt for the server the first time it connects.

VS Code (GitHub Copilot)

Add the server to .vscode/mcp.json in your workspace, or to your user MCP configuration:

{
  "servers": {
    "datapulse": {
      "type": "http",
      "url": "https://mcp.datapulse.global"
    }
  }
}

opencode

Add the server to opencode.json (or ~/.config/opencode/opencode.json to use it in every project):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "datapulse": {
      "type": "remote",
      "url": "https://mcp.datapulse.global",
      "timeout": 60000
    }
  }
}

Then log in:

opencode mcp auth datapulse

opencode allows 5 seconds per MCP request by default. Some DataPulse tools take longer than that. A first datapulse_domain_overview for a domain takes 15–30 seconds, and a synchronous scrape can wait up to 50. Set timeout as shown above.

Other clients

Any MCP client that supports remote servers with OAuth can connect to https://mcp.datapulse.global directly. For a client that only runs local (stdio) servers, use the mcp-remote bridge as the server command:

{
  "mcpServers": {
    "datapulse": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.datapulse.global"]
    }
  }
}

Checking the connection

Ask your assistant something like “Use DataPulse to give me an overview of example.com”. It should call datapulse_domain_overview and summarize the site, its DNS and its registration. To see what the server can do, ask it to “read the DataPulse MCP help”. It will call datapulse_help, which returns the same material as the guides.

How sign-in works

The server follows the MCP authorization specification, so clients configure sign-in themselves:

• OAuth 2.1 authorization code flow with PKCE (S256). Public clients need no client secret.
• Dynamic client registration at https://mcp.datapulse.global/register, so you don’t have to create an OAuth application.
• Discovery through /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
• Refresh tokens. Clients that request offline_access stay signed in without logging in again each session.

Scopes

Each tool needs one OAuth scope. The tool reference shows the scope on every tool page.

datapulse_help and the ICANN Applicant Guidebook tools need no scope. Clients normally request every scope the server advertises (datapulse:mcp, datapulse:dns, datapulse:scrape, …). Which tools actually work for you depends on your DataPulse plan.

Troubleshooting

401 Unauthorized. Your access token is missing or has expired. Reconnect or log in to the server again from your client. For example, use /mcp in Claude Code or opencode mcp auth datapulse.

403 Forbidden, or a tool reports missing permissions. You are signed in, but your plan doesn’t include that tool. See Pricing, or check your account at /app/. If calls that worked earlier start failing, you may have used up today’s MCP credits.

The login page reports a callback URL mismatch. The redirect URL your client uses wasn’t accepted by DataPulse sign-in. Contact us with the name of your MCP client and the redirect URL shown in the error.

Tool calls time out. Raise your client’s MCP request timeout to 60 seconds or more. See the opencode example above.