Remote MCP · Endpoint

com.drawscheduleworks/site MCP server

No. com.drawscheduleworks/site answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://drawscheduleworks.com/mcp

The last check completed an MCP handshake.

Registry name
com.drawscheduleworks/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
876 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
DrawScheduleWorks: the site's own MCP server — dataset; every answer cites the site.
Website
https://drawscheduleworks.com/
Listing
From the official MCP registry (active).
Recent checks of com.drawscheduleworks/site
CheckedResultHandshake
1 hour agoHandshake completed876 ms
18 hours agoHandshake completed736 ms
2 days agoHandshake completed614 ms
3 days agoHandshake completed499 ms
4 days agoHandshake completed2.13 s
5 days agoHandshake completed1.27 s
6 days agoHandshake completed821 ms
7 days agoHandshake completed1.52 s
10 days agoHandshake completed1.02 s
13 days agoHandshake completed2.09 s
15 days agoHandshake completed777 ms
17 days agoHandshake completed512 ms
19 days agoHandshake completed692 ms
21 days agoHandshake completed828 ms
23 days agoHandshake completed930 ms
25 days agoHandshake completed911 ms
27 days agoHandshake completed836 ms
28 days agoHandshake completed768 ms
29 days agoHandshake completed1.27 s

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 24 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.drawscheduleworks/site and makes no claim about it beyond what these checks measured.