_ registry / mcp streamable-http · checked 55m ago

spywinads

https://spywinads.com

Registry code: aa54377be63850e3

api record

SpyWinAds checks Facebook video ads for online sellers: a video's real age (when the file was first uploaded to Meta) and every store running the same video. US Meta ads only. Read-only. Data: Meta (Facebook, Instagram) ads shown in the US, from the SpyWinAds library (ads scanned by SpyWinAds users). Counts are minimums of ads observed, not sales. No ad spend, reach, orders or revenue data. These numbers do not show whether a product sells or makes a profit: many live or new ads can mean heavy testing, and a video run by many stores is copied, not proven. 'Earliest store' means earliest in…

endpoint
https://spywinads.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is spywinads live?
Yes — it answered the hub's last check (checked 55m ago). It answered 100% of checks over the last 30 days.
Is spywinads free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does spywinads have?
5 tools: spywin_spy_store_ads, spywin_export_shopify_product, spywin_get_video_reuse_research, spywin_get_page_ads, spywin_lookup_video_ad.
Is spywinads safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
819ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open2 auth-required 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • spywin_get_video_reuse_research open 55m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • spywin_get_page_ads auth-required 55m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "page"
  ],
  "properties": {
    "page": {
      "type": "string",
      "description": "Facebook Page link (https://www.facebook.com/...) or numeric Page ID"
    }
  }
}
    arguments 12 lines
  • spywin_lookup_video_ad auth-required 55m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ad"
  ],
  "properties": {
    "ad": {
      "type": "string",
      "description": "Meta Ad Library link (https://www.facebook.com/ads/library/?id=...) or the numeric ad ID"
    }
  }
}
    arguments 12 lines
  • spywin_spy_store_ads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Store domain, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • spywin_export_shopify_product unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Product URL, e.g. https://store.com/products/handle"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id aa54377be63850e3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa54377be63850e3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aa54377be63850e3/badge.svg)](https://brick.blue/agent/aa54377be63850e3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.