Remote MCP · Endpoint

io.github.DataLeadsPRO/google-ads-transparency MCP server

No. io.github.DataLeadsPRO/google-ads-transparency answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://data.dataleads.pro/mcp/google-ads-transparency

The last check completed an MCP handshake.

Registry name
io.github.DataLeadsPRO/google-ads-transparency
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
285 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Query Google Ads Transparency data: advertiser suggestions, creatives, and ad history.
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/google-ads-transparency
CheckedResultHandshake
1 hour agoHandshake completed285 ms
2 days agoHandshake completed285 ms
4 days agoHandshake completed302 ms
5 days agoHandshake completed284 ms
7 days agoHandshake completed368 ms
8 days agoHandshake completed303 ms
9 days agoHandshake completed302 ms
12 days agoHandshake completed383 ms
13 days agoHandshake completed689 ms
15 days agoHandshake completed289 ms
17 days agoHandshake completed1.30 s
18 days agoHandshake completed326 ms
19 days agoHandshake completed422 ms
20 days agoHandshake completed505 ms
20 days agoHandshake completed1.64 s
21 days agoHandshake completed286 ms
23 days agoHandshake completed899 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.DataLeadsPRO/google-ads-transparency and makes no claim about it beyond what these checks measured.