Remote MCP · Endpoint
io.github.getgapup/mcp-knowledge MCP server
No. io.github.getgapup/mcp-knowledge answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.gapup.io/
The last check completed an MCP handshake.
- Registry name
- io.github.getgapup/mcp-knowledge
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 500 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 58.8% from 17 checks
- Described by its publisher as
- 100+ MCP tools for AI agents: content metadata, trade intelligence, business-expertise analysis.
- Repository
- https://github.com/getgapup/gapup-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 500 ms |
| 2 days ago | Handshake completed | 437 ms |
| 4 days ago | Handshake completed | 141 ms |
| 5 days ago | Handshake completed | 417 ms |
| 7 days ago | Handshake completed | 460 ms |
| 8 days ago | Handshake completed | 438 ms |
| 9 days ago | Handshake completed | 136 ms |
| 12 days ago | Handshake completed | 442 ms |
| 13 days ago | Handshake completed | 929 ms |
| 15 days ago | Handshake completed | 302 ms |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 10 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.getgapup/mcp-knowledge and makes no claim about it beyond what these checks measured.