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.

SpyWinAds

REMOTE · SPYWINADS.COM

Facebook video ad intel: a video ad's real age and every store running the same video.

Available components

+4 this week 84 Trust /100

Last scanned (13 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

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 Security97
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 560 tokens (~112/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 29 Oct 26 80

    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://spywinads.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=spywinads.com CN=YE1,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 668fbf1346fa20f01a23b054ba2c3290b5a
SANs: *.spywinads.com, spywinads.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of spywinads.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
spywinads.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Sign in to SpyWinAds to use this tool", resource_metadata="https://spywinads.com/.well-known/oauth-protected-resource/mcp", scope="ads:read product:export"

Bearer error="invalid_token", error_description="Sign in to SpyWinAds to use this tool", resource_metadata="https://spywinads.com/.well-known/oauth-protected-resource/mcp", scope="ads:read product:export"
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'none'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Protected resource metadata

Document https://spywinads.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://spywinads.com/mcp
Authorisation server https://spywinads.com

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spywinads.com/mcp Verified 200
http (plaintext) http://spywinads.com/mcp HTTPS enforced 301 https://spywinads.com/mcp
MCP tools · 5 exposed · ~413 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
spywin_export_shopify_product ~79

Read a public Shopify product page and return its title, prices, variants and images, plus a download link to a Shopify-import CSV (valid 24 hours) and the product's video ads if the SpyWinAds library has them.

NameTypeReqDescription
urlstringyesProduct URL, e.g. https://store.com/products/handle

No output schema declared.

No examples provided.

spywin_get_page_ads ~73

See the video ads a Facebook Page runs: total and live ads, videos, top videos with real age, and the stores the Page sends traffic to. Input: Facebook Page link or Page ID.

NameTypeReqDescription
pagestringyesFacebook Page link (https://www.facebook.com/...) or numeric Page ID

No output schema declared.

No examples provided.

spywin_get_video_reuse_research ~61

Headline numbers from SpyWinAds Research 'Video Reuse Index': how often Facebook video ads are old videos brought back, how many stores share a video, and how fast a video spreads to 5 stores. With method link.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

spywin_lookup_video_ad ~119

Check how old a Facebook video ad really is and which stores run the same video. Input: a Meta Ad Library link or ad ID. Returns the day the video file was first uploaded to Facebook (accurate to 1-2 days), the first ad date, live ads, how many stores run the same video now and ever, and the earliest stores in the SpyWinAds library.

NameTypeReqDescription
adstringyesMeta Ad Library link (https://www.facebook.com/ads/library/?id=...) or the numeric ad ID

No output schema declared.

No examples provided.

spywin_spy_store_ads ~81

See the Facebook video ads a Shopify / online store is running. Input: the store domain. Returns live ads, new ads in 7 days, number of videos, products and Pages, and the top videos with their real age and how many stores run each one.

NameTypeReqDescription
domainstringyesStore domain, e.g. example.com

No output schema declared.

No examples provided.

Install

How do I install the SpyWinAds MCP server?

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

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

What is the SpyWinAds MCP server?

SpyWinAds is an MCP server listed in the public MCP registry as com.spywinads/mcp. Facebook video ad intel: a video ad's real age and every store running the same video. This page covers its hosted endpoint (https://spywinads.com/mcp).

Is the SpyWinAds MCP server safe to use?

SpyWinAds scores 84 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 SpyWinAds MCP server expose?

SpyWinAds exposes 5 tools: spywin_lookup_video_ad, spywin_spy_store_ads, spywin_get_page_ads, spywin_export_shopify_product, spywin_get_video_reuse_research. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.

Does the SpyWinAds MCP server require authentication?

Yes. SpyWinAds asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the SpyWinAds MCP server still maintained?

SpyWinAds 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.

What did VerifyMCP test on the SpyWinAds MCP server?

VerifyMCP ran 13 checks on SpyWinAds, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.