Remote MCP · Endpoint

Ad Radar MCP server

No. Ad Radar answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://app.ad-radar.dev/api/mcp

The last check completed an MCP handshake.

Registry name
dev.ad-radar/ad-radar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
262 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search winning Meta ads with $50k+ in estimated spend, read hooks and scripts, and draft briefs.
Website
https://ad-radar.dev/mcp
Listing
From the official MCP registry (active).
Recent checks of Ad Radar
CheckedResultHandshake
5 hours agoHandshake completed262 ms
2 days agoHandshake completed134 ms
5 days agoHandshake completed71 ms
7 days agoHandshake completed62 ms
9 days agoHandshake completed93 ms
11 days agoHandshake completed79 ms
13 days agoHandshake completed66 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed71 ms
18 days agoHandshake completed110 ms
20 days agoHandshake completed79 ms
21 days agoHandshake completed1.16 s
23 days agoCredentials required—

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Ad Radar and makes no claim about it beyond what these checks measured.