Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ProWebLook

REMOTE · MCP.PROWEBLOOK.COM

19 tools for phone, WhatsApp, email, caller ID, IP geo, blacklist, scraping & SERP

60 Trust /100

Last scanned (9 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2653 tokens (~139/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 58

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://mcp.proweblook.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=proweblook.com CN=WE1,O=Google Trust Services,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 2cd50da4f185f3080eabc0e6d7e0ec1f
SANs: proweblook.com, mcp.proweblook.com, *.mcp.proweblook.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.proweblook.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
proweblook.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.proweblook.com/mcp Verified 200
http (plaintext) http://mcp.proweblook.com/mcp Inconclusive 405
MCP tools · 19 exposed · ~2,395 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
caller_id_lookup ~72

Reverse phone lookup: retrieve the registered caller name (CNAM) associated with a phone number. Costs 1 caller-ID credit per call. Use to identify who owns a number.

NameTypeReqDescription
phone_numberstringyesPhone number to look up, in E.164 (+14155552671) or local format.

No output schema declared.

No examples provided.

check_blacklist ~155

Check an IP address, domain, or URL against major global blacklists and spam databases (DNSBL/RBL sources). Returns per-source listed/clean results and an overall summary. Costs 1 blacklist credit per successful check. Use for deliverability debugging, reputation checks, and abuse triage.

NameTypeReqDescription
sourcesstring–Optional comma-separated list of specific blacklist source identifiers to check instead of the full default set.
targetstringyesThe IP address, domain, or URL to check (e.g. "192.0.2.1", "example.com", "https://example.com/page").
target_typestring–What kind of target this is. Default "auto" detects it for you.

No output schema declared.

No examples provided.

check_spam_score ~109

Analyze email subject and/or body text for spam trigger words and get a 0-100 spam score, a risk level (Low/Medium/High Risk), and a per-trigger breakdown. Costs 1 spam-checker credit per successful request. Use before sending marketing/transactional email to predict deliverability. At least one of subject or content must be provided.

NameTypeReqDescription
contentstring–The email body text to analyze.
subjectstring–The email subject line to analyze.

No output schema declared.

No examples provided.

check_whatsapp ~131

Check whether a phone number has an active WhatsApp account (without sending any message or OTP), including whether it is a WhatsApp Business account. Also returns phone enrichment (carrier, line type, country). Costs 1 WA credit per successful call. Response fields: numberstatus (true = on WhatsApp), businessnumber (true = business account).

NameTypeReqDescription
country_codestring–ISO 3166-1 alpha-2 country hint when phone_number is in local format.
phone_numberstringyesPhone number to check, in E.164 (+14155552671) or local format.

No output schema declared.

No examples provided.

geo_ip ~90

Look up geolocation, ISP, and organization details for an IPv4 or IPv6 address (country, region, city, coordinates, timezone, ASN). Deducts from your Geo-IP quota. Use for traffic analysis, fraud checks, or localizing users.

NameTypeReqDescription
ipstringyesThe IPv4 or IPv6 address to look up (e.g. "8.8.8.8").

No output schema declared.

No examples provided.

get_balance ~87

Check remaining ProWebLook API credits for a service. Free (consumes no credits). Only these services are supported here: phonevalidation, wavalidation, calleridvalidation, blacklistchecker. Most other tools (scraping, spam, SERP, social, audits) return your remaining balance inside their own responses.

NameTypeReqDescription
servicestringyesService to check the credit balance for.

No output schema declared.

No examples provided.

get_brand_audit ~114

Get the status/results of an AI Visibility Audit by audit_id. Free to call. Use detail "summary" (default) while polling — it returns progress and job_status; once job_status is "completed", call again with detail "full" for the complete report (visibility score, per-LLM coverage, competitive benchmarking, query results, recommendations).

NameTypeReqDescription
audit_idstringyesThe audit_id returned by run_brand_audit.
detailstring–How much detail to return. Default "summary".

No output schema declared.

No examples provided.

get_brand_trend ~77

Get the historical AI-visibility score trend (up to 90 data points) for a brand + domain that has been audited before. Free to call. Use to show visibility change over time.

NameTypeReqDescription
brandstringyesThe brand name used in past audits.
domainstringyesThe bare domain used in past audits.

No output schema declared.

No examples provided.

get_social_post ~77

Fetch the full content of a single public Reddit, X (Twitter), or LinkedIn post by its URL, including replies/comments where available. Costs 1 scraper credit per successful call.

NameTypeReqDescription
platformstring–Platform the URL belongs to. Default "reddit".
urlstringyesThe full URL of the post to fetch.

No output schema declared.

No examples provided.

get_x_comments ~102

Fetch comments/replies for a single X (Twitter) post URL. Costs 1 scraper credit per successful call. Use after finding a post with search_social (platform "x") to read its discussion thread.

NameTypeReqDescription
maxCommentsinteger–Maximum comments to return. Default 20.
maxItemsinteger–Maximum top-level items to return. Default 10.
urlstringyesThe full URL of the X (Twitter) post.

No output schema declared.

No examples provided.

google_serp ~192

Run a Google search and get structured organic results (title, URL, snippet, position) as JSON. Costs 1 SERP credit per successful search. Use for rank tracking, competitor research, or finding sources on a topic. Pagination: start must be a multiple of 10 (0 = first page).

NameTypeReqDescription
countrystring–Country to localize results for (gl).
devicestring–Device type to emulate. Default "desktop".
domainstring–Google domain to search on. Default "google.com".
languagestring–Result language (hl). Default "en".
numinteger–Number of results to return (10-100). Default 10.
querystringyesThe search query (1-2000 characters).
startinteger–Result offset for pagination — must be a multiple of 10. Default 0.

No output schema declared.

No examples provided.

list_brand_audits ~79

List this account's past AI Visibility Audits (paginated, newest first). Free to call. Useful for finding an earlier audit_id instead of re-running (and re-paying for) an audit.

NameTypeReqDescription
pageinteger–Page number. Default 1.
per_pageinteger–Results per page (1-50).

No output schema declared.

No examples provided.

run_brand_audit ~266

Start an AI Visibility Audit: measures how visible a brand is in AI assistant answers (ChatGPT, Claude, Gemini, Perplexity) across a set of queries, with competitor benchmarking and recommendations. Costs 1 audit credit. Asynchronous — returns an audit_id immediately; audits take several minutes. Poll with get_brand_audit (detail "summary") until job_status is "completed", then fetch detail "full". Identical requests within 24h may return a cached audit.

NameTypeReqDescription
brandstringyesThe brand name to audit (e.g. "ProWebLook").
competitorsarray–Up to 5 competitor brand names to benchmark against.
domainstringyesThe brand's bare domain (e.g. "proweblook.com" — no scheme or path).
industrystring–Industry/category context (e.g. "API SaaS", "running shoes").
llmsarray–Which LLM providers to test against (see the audit docs for supported values). Leave empty for all enabled providers.
queriesarray–Specific user queries to test. Leave empty to have relevant queries auto-generated.
sample_sizeinteger–Samples per query per LLM (1-10). Default 3.

No output schema declared.

No examples provided.

scrape_url ~210

Scrape any web page: get clean Markdown, rendered/raw HTML, all links, SEO metadata, and/or a full-page screenshot in a single call. Costs 1 scraping credit per successful request regardless of how many formats you ask for. Screenshots use a full Chromium render (~5-15s); other formats are faster (~1-5s). Screenshots are returned as an image attachment. Use for reading article content, extracting page metadata, link discovery, or visual captures.

NameTypeReqDescription
formatsarray–Output formats to return. Default ["markdown", "metadata"].
onlyMainContentboolean–Strip navigation/footer/ads, keeping only the main article content. Default true.
timeoutinteger–Maximum milliseconds for the entire scrape. Default 30000.
urlstringyesFull URL to scrape. Must start with http:// or https://.
waitForinteger–Extra milliseconds to wait after page load (for lazy-loaded content). Default 0.

No output schema declared.

No examples provided.

search_social ~197

Search public posts on Reddit, X (Twitter), or LinkedIn by keyword. Returns post items (title/text, author, URL, engagement) plus meta. Costs 1 scraper credit per successful search. Use for social listening, market research, or finding discussions about a topic or brand.

NameTypeReqDescription
maxItemsinteger–Maximum results to return (1-50). Default 10.
platformstring–Platform to search. Default "reddit".
querystringyesSearch keywords.
sortstring–Sort order (platform-dependent, e.g. "new", "top", "relevance"). Default "new".
subredditsstring–Reddit only: comma-separated subreddit names to restrict the search to (e.g. "webdev,programming").
timestring–Time window (e.g. "day", "week", "month", "all"). Default "week".

No output schema declared.

No examples provided.

validate_phone ~197

Validate a phone number and enrich it with carrier, line type (mobile/landline/voip), country, location, timezone, and national/international formatting. Costs 1 phone-validation credit per successful call. Use when you need to know whether a number is real, who operates it, or where it is registered.

NameTypeReqDescription
country_codestring–Optional ISO 3166-1 alpha-2 country hint (for example, "US" or "IN") for a local/national phone_number. This is not a numeric calling prefix such as +91. Omit it, or use the literal "none", only with…
phone_numberstringyesPhone number to validate. When country_code is omitted or set to none, provide the full international number including its country calling code, preferably E.164 (for example, +14155552671). A local…

No output schema declared.

No examples provided.

verify_email ~63

Verify an email address: syntax, MX records, SMTP deliverability, and disposable-address detection. Costs 1 email credit per successful check. Use to validate signup emails or clean mailing lists one address at a time.

NameTypeReqDescription
emailstringyesThe email address to verify.

No output schema declared.

No examples provided.

whatsapp_batch_status ~82

Poll the status and results of a WhatsApp batch validation job created with whatsapp_batch_submit. Free to call. Poll every 5-10 seconds for small batches, 30-60 seconds for large ones, until status is "completed"; results are included once done.

NameTypeReqDescription
batch_idstringyesThe batch_id (UUID) returned by whatsapp_batch_submit.

No output schema declared.

No examples provided.

whatsapp_batch_submit ~95

Submit up to 1,000 phone numbers for asynchronous WhatsApp validation. Deducts 1 WA credit PER NUMBER upfront (the whole batch is rejected if the balance is insufficient), so confirm quantities before submitting large batches. Returns a batch_id immediately with status "processing" — retrieve results with whatsapp_batch_status.

NameTypeReqDescription
phone_numbersarrayyesPhone numbers to validate (duplicates are removed automatically). Max 1,000.

No output schema declared.

No examples provided.

Install

How do I install the ProWebLook MCP server?

ProWebLook is a hosted endpoint at https://mcp.proweblook.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.proweblook.com

# add to Claude Code
claude mcp add --transport http dubeychandan996-proweblook 'https://mcp.proweblook.com/mcp'
Common questions

What is the ProWebLook MCP server?

ProWebLook is an MCP server listed in the public MCP registry as io.github.dubeychandan996/proweblook. 19 tools for phone, WhatsApp, email, caller ID, IP geo, blacklist, scraping & SERP. This page covers its hosted endpoint (https://mcp.proweblook.com/mcp).

Is the ProWebLook MCP server safe to use?

ProWebLook scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ProWebLook MCP server expose?

ProWebLook exposes 19 tools: validate_phone, caller_id_lookup, check_whatsapp, whatsapp_batch_submit, whatsapp_batch_status, and 14 more. Their descriptions and schemas cost roughly 2,395 tokens of context every time the server is loaded.

Does the ProWebLook MCP server require authentication?

No. We connected to ProWebLook without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ProWebLook MCP server still maintained?

ProWebLook is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.