Remote MCP · Endpoint

Ad Angle Map MCP server

No. Ad Angle Map answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://adangle.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/ad-angle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
299 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
See how competitors position a product before you write ads.
Listing
From the official MCP registry (active).
Recent checks of Ad Angle Map
CheckedResultHandshake
2 hours agoHandshake completed299 ms
1 day agoHandshake completed353 ms
4 days agoHandshake completed4.31 s
6 days agoHandshake completed169 ms
9 days agoHandshake completed257 ms
11 days agoHandshake completed188 ms
13 days agoHandshake completed371 ms
15 days agoHandshake completed309 ms
17 days agoHandshake completed1.08 s
19 days agoHandshake completed50 ms
21 days agoHandshake completed711 ms
22 days agoHandshake completed365 ms
24 days agoHandshake completed563 ms
25 days agoHandshake completed754 ms
27 days agoHandshake completed293 ms

The last 15 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 Ad Angle Map and makes no claim about it beyond what these checks measured.