Remote MCP · Endpoint
Mako Metrics MCP server
No. Mako Metrics answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ufupdlaxddckqxbgbhwu.supabase.co/functions/v1/mcp
The last check completed an MCP handshake.
- Registry name
- com.makometrics/mako-metrics
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 333 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Competitor Meta ads intelligence reports. List plans, create orders, Stripe checkout for humans.
- Website
- https://makometrics.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 333 ms |
| 18 hours ago | Handshake completed | 244 ms |
| 2 days ago | Handshake completed | 285 ms |
| 3 days ago | Handshake completed | 293 ms |
| 4 days ago | Handshake completed | 281 ms |
| 5 days ago | Handshake completed | 434 ms |
| 6 days ago | Handshake completed | 299 ms |
| 7 days ago | Handshake completed | 307 ms |
| 10 days ago | Handshake completed | 239 ms |
| 13 days ago | Handshake completed | 315 ms |
| 15 days ago | Handshake completed | 350 ms |
| 17 days ago | Handshake completed | 323 ms |
| 19 days ago | Handshake completed | 301 ms |
| 21 days ago | Handshake completed | 355 ms |
| 23 days ago | Handshake completed | 286 ms |
| 25 days ago | Handshake completed | 245 ms |
| 27 days ago | Handshake completed | 301 ms |
| 28 days ago | Handshake completed | 331 ms |
| 29 days ago | Handshake completed | 406 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Mako Metrics and makes no claim about it beyond what these checks measured.