MCP Server - ProWebLook API

Two different MCP URLs — don’t mix them up. https://docs.proweblook.com/mcp is Mintlify’s auto-hosted documentation-search connector: it can only search these docs and cannot execute APIs. To actually run ProWebLook APIs (validate phones, check WhatsApp, verify emails, scrape, etc.), connect to https://mcp.proweblook.com/mcp — the server documented on this page.

Overview

ProWebLook runs a remote MCP (Model Context Protocol) server that exposes 19 ProWebLook APIs as tools any MCP-compatible AI client can call — Claude Code, claude.ai, ChatGPT, Cursor, VS Code, Windsurf, and more.

Endpoint: https://mcp.proweblook.com/mcp (both / and /mcp work)
Transport: Streamable HTTP (stateless JSON-RPC)
Health check: GET https://mcp.proweblook.com/healthz

initialize and tools/list work without an API key, so clients can discover the tools before you authenticate. tools/call requires a key — without one it returns an instructive error telling you how to authenticate.

Authentication

Use your regular ProWebLook API key (get one free at proweblook.com). The server checks credentials in this order:

Authorization: Bearer <API_KEY> header — preferred
X-API-KEY: <API_KEY> header
?api_key=<API_KEY> URL parameter — fallback for clients that cannot send custom headers

With the ?api_key= form, the URL itself contains a secret — treat it like a password. It can end up in client config files, logs, and browser history. Prefer the Authorization: Bearer header whenever your client supports custom headers.

Rotating your API key breaks any saved connector configuration that embeds the old key (headers or URL). After a rotation, update the key in every client where you added the connector.

Connect your client

Replace YOUR_API_KEY with your ProWebLook API key.

Run this one-liner in your terminal:

claude mcp add --transport http proweblook https://mcp.proweblook.com/mcp --header "Authorization: Bearer YOUR_API_KEY"

In claude.ai (web or desktop): Settings → Connectors → Add custom connector, then enter this URL:

https://mcp.proweblook.com/mcp?api_key=YOUR_API_KEY

claude.ai custom connectors do not support custom headers, so the key rides in the URL — keep the URL secret.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "proweblook": {
      "url": "https://mcp.proweblook.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

In ChatGPT: Settings → Connectors → Developer mode, then add the connector with this URL:

https://mcp.proweblook.com/mcp?api_key=YOUR_API_KEY

Add to .vscode/mcp.json:

{
  "servers": {
    "proweblook": {
      "type": "http",
      "url": "https://mcp.proweblook.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "proweblook": {
      "serverUrl": "https://mcp.proweblook.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Any other client that cannot send headers: append ?api_key=YOUR_API_KEY to the endpoint URL. Remember that the URL then contains a secret.

Available tools

Tool	Description	Credits
`validate_phone`	Phone validation with carrier, line type, country, and timezone	1 phone-validation credit
`caller_id_lookup`	Reverse phone lookup (CNAM caller name)	1 caller-ID credit
`check_whatsapp`	Is a number on WhatsApp (+ Business account detection); no OTP sent	1 WA credit
`whatsapp_batch_submit`	Async batch WhatsApp validation, up to 1,000 numbers	1 WA credit per number (deducted upfront)
`whatsapp_batch_status`	Poll batch results	Free
`verify_email`	Email verification (MX/SMTP/disposable detection)	1 email credit
`check_blacklist`	Check an IP/domain/URL against global blacklists	1 blacklist credit
`check_spam_score`	0–100 spam score for an email subject/body	1 spam-checker credit
`geo_ip`	IP geolocation (country, city, ISP, ASN)	Geo-IP quota
`scrape_url`	Scrape any URL: markdown/html/links/metadata/screenshot	1 scraping credit
`search_social`	Keyword search across Reddit / X / LinkedIn	1 scraper credit
`get_social_post`	Fetch a single social post by URL	1 scraper credit
`get_x_comments`	Fetch the comments of an X post	1 scraper credit
`google_serp`	Structured Google search results	1 SERP credit
`run_brand_audit`	Start an async AI-visibility audit (ChatGPT/Claude/Gemini/Perplexity)	1 audit credit
`get_brand_audit`	Poll audit status / fetch the full report	Free
`list_brand_audits`	List past audits	Free
`get_brand_trend`	Visibility score trend over time	Free
`get_balance`	Remaining credits for phonevalidation / wavalidation / calleridvalidation / blacklistchecker	Free

Billing & metering

There is no separate MCP plan or MCP billing. Each tool call debits the existing per-product credit balance of the account that owns the API key — exactly as if you had called the underlying REST API directly. Free-metadata tools (batch/audit polling, listings, get_balance) cost nothing. Get an API key and manage your balances on the dashboard at proweblook.com — a free tier is available.

Troubleshooting

Symptom	Cause	Fix
`401` / “rejected the API key”	Key is wrong or has been rotated	Copy a fresh key from the dashboard and update your client config
”Out of credits” error from a tool	The per-product balance for that tool is empty	Top up that product on the dashboard
Client connects but shows 0 tools (or only docs search)	Client is pointed at `docs.proweblook.com/mcp` (search-only)	Change the URL to `https://mcp.proweblook.com/mcp`
Header auth fails behind a corporate proxy	Proxy strips the `Authorization` header	Use the `?api_key=YOUR_API_KEY` URL form instead

​Overview

​Authentication

​Connect your client

​Available tools

​Billing & metering

​Troubleshooting

Overview

Authentication

Connect your client

Available tools

Billing & metering

Troubleshooting