Remote MCP · Endpoint

AdsTurbo MCP server

No. AdsTurbo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://adsturbo.ai/klian/novartapi/mcp

The last check completed an MCP handshake.

Registry name
io.github.AdsTurbo/adsturbo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
617 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI ad creatives: clone reference ads, AI spokesperson videos, video generation, translation, images.
Listing
From the official MCP registry (active).
Recent checks of AdsTurbo
CheckedResultHandshake
1 hour agoHandshake completed617 ms
1 day agoHandshake completed722 ms
1 day agoHandshake completed607 ms
3 days agoHandshake completed604 ms
6 days agoHandshake completed625 ms
8 days agoHandshake completed691 ms
11 days agoHandshake completed688 ms
13 days agoHandshake completed682 ms
15 days agoHandshake completed669 ms
17 days agoHandshake completed679 ms
19 days agoHandshake completed668 ms
21 days agoHandshake completed663 ms
23 days agoHandshake completed665 ms
24 days agoHandshake completed666 ms

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

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 AdsTurbo and makes no claim about it beyond what these checks measured.