Remote MCP · Endpoint
io.github.mrkeyoor/should-i-use MCP server
No. io.github.mrkeyoor/should-i-use answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mrkeyoor.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.mrkeyoor/should-i-use
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 667 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Honest library picks for coding agents in 25-360 tokens. Tells your agent what NOT to install.
- Website
- https://mrkeyoor.com/libs/
- Repository
- https://github.com/mrkeyoor/should-i-use
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 667 ms |
| 2 days ago | Handshake completed | 631 ms |
| 4 days ago | Handshake completed | 611 ms |
| 5 days ago | Handshake completed | 602 ms |
| 7 days ago | Handshake completed | 711 ms |
| 8 days ago | Handshake completed | 642 ms |
| 9 days ago | Handshake completed | 690 ms |
| 12 days ago | Handshake completed | 679 ms |
| 13 days ago | Handshake completed | 652 ms |
| 15 days ago | Handshake completed | 656 ms |
| 17 days ago | Handshake completed | 651 ms |
| 18 days ago | Handshake completed | 651 ms |
| 19 days ago | Handshake completed | 689 ms |
| 20 days ago | Handshake completed | 685 ms |
| 20 days ago | Handshake completed | 641 ms |
| 21 days ago | Handshake completed | 651 ms |
| 23 days ago | Handshake completed | 693 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 io.github.mrkeyoor/should-i-use and makes no claim about it beyond what these checks measured.