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.

AdvertiserLeads

REMOTE · ADVERTISERLEADS.COM

Ecommerce brands that just started, scaled or stopped Meta ads, with store platform and pixels

69 Trust /100

Last scanned (9 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 887 tokens (~126/item across 7 items; 5 tools + 2 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
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.

  • 4 Nov 26 +3
    • Schema quality: 168 → 126 ▲ functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • New resource “brand” functional
    • New resource “signals” functional
  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_signals” rewrote its description, which is the text the model reads security
    • Schema quality: 644 → 844 ▼ functional
    • New tool “reveal_brand” functional
    • “search_signals” reworded the description of “niche” cosmetic
  • 2 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 65

    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 5 Nov 2026 · Probed https://advertiserleads.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=advertiserleads.com CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 acd40c9ae49c12840e078035dbb9de60
SANs: advertiserleads.com, www.advertiserleads.com, *.www.advertiserleads.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 advertiserleads.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
advertiserleads.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://advertiserleads.com/mcp Verified 200
http (plaintext) http://advertiserleads.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~695 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
check_store ~116

Store platform (Shopify, WooCommerce, BigCommerce, other store or not a store), catalog size, price range and store age for a domain, plus the tracking pixels and marketing tools on its homepage (Meta, Google Ads, TikTok, Pinterest, Klaviyo, Triple Whale and more). Results under a day old are reused; fresh checks are limited per day (10 without signing in, 50 signed in).

NameTypeReqDescription
domainstringyesThe store's domain, e.g. brand.com. A URL works too.

No output schema declared.

No examples provided.

list_niches ~36

The niches AdvertiserLeads tracks, the signal types and filter values search_signals accepts, and what the caller's plan includes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_brand ~117

Is this store running Meta ads? Finds the Facebook page behind a store domain and returns advertising since, live ads, trend (new, scaling, stable, stopped), channels and store platform. Signed in: catalog size, price range, recent launches and store age (free plan: 5 new domains a day); Pro and up also get recent ads. Unknown domains are checked live in the Meta Ad Library, within a daily limit.

NameTypeReqDescription
domainstringyesThe store's domain, e.g. brand.com. A URL works too.

No output schema declared.

No examples provided.

reveal_brand ~122

Unmasks one brand from search_signals on the free plan: its name, domain, store and Ad Library link. Pass the masked row's ref. Spends one of the account's 10 reveals a month (they reset on the 1st; a brand already revealed is free) and needs a signed-in free account. A revealed brand stays unmasked in later searches, and lookup_brand on its domain shows the full brand detail. Paid plans already see every brand.

NameTypeReqDescription
refstringyesThe ref of a masked row from search_signals.

No output schema declared.

No examples provided.

search_signals ~304

US ecommerce brands flagged on the latest day for a change in their Meta (Facebook/Instagram) ads: newly advertising, scaling, struggling or stopped, with store platform, live ad count and other ad channels. Defaults to new and scaling brands in every niche the caller's plan covers. Without signing in or on the free plan, brand names and domains are masked and only the niche filter applies; each masked row has a ref that reveal_brand unmasks with one of the free plan's monthly reveals. On paid plans each brand returned counts toward the account's monthly export rows (the same brand again that month is free).

NameTypeReqDescription
limitinteger–Rows to return, default 25. Masked results return at most 50.
min_adsinteger–At least this many live ads. Paid plans only.
nichestring–One niche; all of the caller's niches when left out. An account that hasn't picked a niche yet must pass one, and it becomes the account's niche.
offsetinteger–Rows to skip, for paging.
pixelstring–Also advertises on this channel (tracking pixel on the store). Paid plans only.
platformstring–Store platform. Paid plans only.
qstring–Brand name or domain contains this text. Paid plans only.
signalstring–One signal type; newly_advertising and scaling when left out. Paid plans only.

No output schema declared.

No examples provided.

Install

How do I install the AdvertiserLeads MCP server?

AdvertiserLeads is a hosted endpoint at https://advertiserleads.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 · advertiserleads.com

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

What is the AdvertiserLeads MCP server?

AdvertiserLeads is an MCP server listed in the public MCP registry as com.advertiserleads/mcp. Ecommerce brands that just started, scaled or stopped Meta ads, with store platform and pixels. This page covers its hosted endpoint (https://advertiserleads.com/mcp).

Is the AdvertiserLeads MCP server safe to use?

AdvertiserLeads scores 69 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 AdvertiserLeads MCP server expose?

AdvertiserLeads exposes 5 tools: search_signals, lookup_brand, check_store, reveal_brand, list_niches. Their descriptions and schemas cost roughly 695 tokens of context every time the server is loaded.

Does the AdvertiserLeads MCP server require authentication?

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

Is the AdvertiserLeads MCP server still maintained?

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