Remote MCP · Endpoint
PersonalKnowHow MCP server
No. PersonalKnowHow answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://personalknowhow-demo.kxtwrdzt6g.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Georgi-Petkov/personalknowhow
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 233 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Live public demo: query one person's learning and work history as a knowledge graph via MCP.
- Website
- https://personalknowhow.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 233 ms |
| 1 day ago | Handshake completed | 530 ms |
| 2 days ago | Handshake completed | 537 ms |
| 3 days ago | Handshake completed | 246 ms |
| 4 days ago | Handshake completed | 262 ms |
| 5 days ago | Handshake completed | 302 ms |
| 6 days ago | Handshake completed | 244 ms |
| 9 days ago | Handshake completed | 280 ms |
| 11 days ago | Handshake completed | 480 ms |
| 14 days ago | Handshake completed | 303 ms |
| 16 days ago | Handshake completed | 612 ms |
| 18 days ago | Handshake completed | 283 ms |
| 20 days ago | Handshake completed | 474 ms |
| 22 days ago | Handshake completed | 388 ms |
| 24 days ago | Handshake completed | 277 ms |
| 26 days ago | Handshake completed | 252 ms |
| 27 days ago | Handshake completed | 456 ms |
| 29 days ago | Handshake completed | 431 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 PersonalKnowHow and makes no claim about it beyond what these checks measured.