Remote MCP · Endpoint

Vazante MCP server

No. Vazante answered an MCP handshake 43 minutes ago.

Up · key neededLast checked 43 minutes ago

Server URL

https://vazante.app/api/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
app.vazante/vazante
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ask Claude or ChatGPT about your Meta, Google and TikTok Ads, and let AI edit campaigns on your OK.
Listing
From the official MCP registry (active).
Recent checks of Vazante
CheckedResultHandshake
43 minutes agoHandshake completed214 ms
9 days agoHandshake completed182 ms
10 days agoHandshake completed180 ms
11 days agoHandshake completed196 ms
12 days agoHandshake completed359 ms
14 days agoHandshake completed216 ms
14 days agoHandshake completed219 ms
15 days agoHandshake completed177 ms
17 days agoHandshake completed241 ms
19 days agoHandshake completed826 ms
21 days agoHandshake completed194 ms
24 days agoHandshake completed279 ms
26 days agoHandshake completed550 ms
28 days agoHandshake completed186 ms

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

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