Remote MCP · Endpoint

Awning MCP server

No. Awning answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.awning.help/mcp

The last check completed an MCP handshake.

Registry name
help.awning/awning
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find and book local services, classes and rentals; businesses set up and manage their pages.
Listing
From the official MCP registry (active).
Recent checks of Awning
CheckedResultHandshake
2 hours agoHandshake completed307 ms
2 days agoHandshake completed304 ms
4 days agoHandshake completed305 ms
6 days agoHandshake completed301 ms
7 days agoHandshake completed334 ms
9 days agoHandshake completed305 ms
10 days agoHandshake completed304 ms
11 days agoHandshake completed307 ms
14 days agoHandshake completed303 ms
15 days agoHandshake completed303 ms
17 days agoHandshake completed306 ms
18 days agoHandshake completed300 ms
19 days agoHandshake completed303 ms
20 days agoHandshake completed304 ms
21 days agoHandshake completed307 ms
22 days agoHandshake completed316 ms
23 days agoHandshake completed329 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 Awning and makes no claim about it beyond what these checks measured.