New · Model Context Protocol

Connect AI agents to every ProWebLook API

Give Claude, ChatGPT, Cursor, VS Code, Windsurf, and other compatible clients access to 19 API-backed tools for validation, enrichment, scraping, search, social data, and brand audits. Use one remote endpoint, your existing API key, and your existing product credits.

Get your free API key Read the docs

Claude Code connection

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

Remote endpoint

https://mcp.proweblook.com/mcp

19registered tools

1remote endpoint

0extra MCP fees

What is MCP?

One predictable way for AI clients to use external tools

Model Context Protocol is an open client-server standard. Instead of building custom glue code for every provider, an MCP-compatible application discovers available tools, calls the one it needs, and receives a structured result.

Client request

A prompt in Claude, Cursor, or another MCP client needs external data.

Tool discovery

The client reads the tools published by the ProWebLook MCP server.

Tool call

The client sends only the parameters required by the selected tool.

Structured result

The server returns data the assistant can use in its response or workflow.

Why ProWebLook MCP

One connection. Every tool. Your credits.

Connect once and let the client choose the right ProWebLook capability for each request.

One endpoint, 19 tools

No product-specific SDKs or separate connectors. One MCP endpoint publishes all nineteen registered tools.

Uses existing credits

Calls draw from the same product balances as direct API usage. MCP does not add a separate routing fee.

Stateless authentication

Your key is forwarded for the current request and is not stored or logged by the MCP Worker.

Tool catalog

19 API-backed tools across 12 capability groups

The cards group related capabilities for easier scanning. Their tool badges add up to the nineteen tools clients receive from tools/list.

19 registered tools

12 grouped capabilities

1 connection

1 tool

Phone validation

Carrier, line type, country, formatting, and timezone metadata.

3 tools

WhatsApp checks

Single checks, batch submission, and batch status tools.

1 tool

Caller ID

Reverse-lookup available caller-name information.

1 tool

Email verification

Mailbox, MX, SMTP, and disposable-address signals.

1 tool

Blacklist check

IP, domain, and URL reputation checks.

1 tool

Spam score

Email spam scoring through a structured tool call.

1 tool

Geo-IP

Location, ISP, and ASN data for an IP address.

1 tool

Web scraping

Extract page content, links, metadata, and screenshots.

3 tools

Social data

Search social content, retrieve posts, and inspect X comments.

1 tool

Google SERP

Return structured Google search results.

4 tools

Brand audits

Run audits, retrieve results, list audits, and review trends.

1 tool

Credit balance

Check the account’s remaining product balances.

Works with MCP clients

Bring your preferred AI application

Use the Authorization header when your client supports it. For clients without custom headers, use the documented URL-key fallback.

Claude ChatGPT Cursor VS Code Windsurf

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

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

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

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

Use this only when the client cannot send a custom Authorization header.

Get started

Connect in three steps

Use the same ProWebLook account and API key you already use for direct API requests.

1 Account

Get your API key

Create an account and copy the API key shown in your ProWebLook dashboard.

2 Connection

Add the remote server

Use https://mcp.proweblook.com/mcp and configure your key with one of the client patterns above.

3 Prompt

Ask for a ProWebLook task

Your client discovers the tools, selects the relevant one, and returns the structured result in context.

Know before connecting

What ProWebLook MCP is—and is not

The MCP server is a standard access layer for ProWebLook’s existing products, not a separate product catalogue or billing system.

Uses your normal product balances

Each tool call consumes credits from the corresponding ProWebLook product. There is no separate MCP balance.

Publishes ProWebLook tools

This server exposes ProWebLook capabilities; it is not a platform for publishing arbitrary third-party APIs.

Does not store your key

The Worker forwards the credential for each request and does not store or log it.

Requires a compatible client

The client must support remote MCP servers and a usable authentication method.

Explore the full platform

Compare products before connecting your agent

Browse phone and messaging, identity and risk, web intelligence, search, social-data, and AI-audit products individually—or call their REST endpoints directly.

View product pricing Browse API reference Open API playground

MCP FAQ

Answers before you connect

Protocol basics, authentication, supported clients, billing, and configuration guidance.

How do MCP servers work?

An MCP server exposes a set of tools through a standard protocol. An MCP client discovers those tools and calls the right one when a user request needs external data. ProWebLook’s server exposes its API-backed tools this way, so one connection can support many different workflows.

What does MCP stand for?

MCP stands for Model Context Protocol, an open standard for connecting AI applications to external tools and data through a predictable client-server interface.

What is the difference between an MCP client and an MCP server?

The MCP client is the AI application—such as Claude, Cursor, ChatGPT, VS Code, or Windsurf—that sends requests. The MCP server is the service that publishes tools and returns structured results. One client can connect to multiple servers.

Is my API key stored when I connect over MCP?

No. The ProWebLook MCP Worker forwards the key with each upstream request and does not store or log it. Bearer-token headers are preferred when the client supports custom headers.

Which AI clients support ProWebLook MCP?

ProWebLook provides connection patterns for Claude, Cursor, ChatGPT, VS Code, and Windsurf. Other clients can connect when they support remote MCP servers and either custom authorization headers or the documented URL-key fallback.

Does MCP cost more than calling the REST API directly?

No additional MCP routing fee is added. Tool calls use the same product-specific credit balances as the corresponding ProWebLook APIs.

Where can I find the MCP documentation?

The ProWebLook MCP documentation contains client setup, authentication, tool schemas, and troubleshooting guidance.

What if my MCP client cannot send custom headers?

Use the documented URL fallback: https://mcp.proweblook.com/mcp?api_key=YOUR_API_KEY. Prefer the Authorization header when possible because URLs can be retained by client history or diagnostic logs.

What are MCP servers used for beyond ProWebLook?

MCP servers can expose files, databases, APIs, development tools, and business systems. ProWebLook’s server is focused on its own phone, messaging, email, IP, scraping, search, social-data, and brand-audit capabilities.

Give your AI agent ProWebLook tools

Create an account for an API key, then use the dashboard or documentation to configure your client.

Start free Go to dashboard