Remote MCP · Endpoint
Rasczak Knowledge Commons MCP server
No. Rasczak Knowledge Commons answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://rasczak-agent-service.rasczak-commons.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.workers.rasczak-commons.rasczak-agent-service/agent-service
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 176 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Free decision methods, work-kit previews and optional feedback. Hosted research is not available.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 176 ms |
| 1 day ago | Handshake completed | 403 ms |
| 2 days ago | Handshake completed | 350 ms |
| 3 days ago | Handshake completed | 58 ms |
| 4 days ago | Handshake completed | 159 ms |
| 5 days ago | Handshake completed | 178 ms |
| 6 days ago | Handshake completed | 89 ms |
| 9 days ago | Handshake completed | 434 ms |
| 12 days ago | Handshake completed | 210 ms |
| 14 days ago | Handshake completed | 646 ms |
| 16 days ago | Handshake completed | 173 ms |
| 18 days ago | Handshake completed | 169 ms |
| 20 days ago | Handshake completed | 450 ms |
| 22 days ago | Handshake completed | 425 ms |
| 24 days ago | Handshake completed | 225 ms |
| 26 days ago | Handshake completed | 253 ms |
| 27 days ago | Handshake completed | 145 ms |
| 28 days ago | Handshake completed | 408 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Rasczak Knowledge Commons and makes no claim about it beyond what these checks measured.