Remote MCP · Endpoint
com.keywordise/keywordise MCP server
No. com.keywordise/keywordise answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://keywordise.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.keywordise/keywordise
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 283 ms
- Tools exposed
- 69 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Auto-apply to jobs: matches your CV, tailors a fresh CV per posting, and applies for you.
- Website
- https://keywordise.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 283 ms |
| 12 hours ago | Handshake completed | 227 ms |
| 1 day ago | Handshake completed | 305 ms |
| 2 days ago | Handshake completed | 259 ms |
| 4 days ago | Handshake completed | 247 ms |
| 4 days ago | Handshake completed | 242 ms |
| 5 days ago | Handshake completed | 255 ms |
| 6 days ago | Handshake completed | 249 ms |
| 8 days ago | Handshake completed | 259 ms |
| 11 days ago | Handshake completed | 156 ms |
| 13 days ago | Handshake completed | 256 ms |
| 16 days ago | Handshake completed | 256 ms |
| 18 days ago | Handshake completed | 296 ms |
| 20 days ago | Handshake completed | 305 ms |
| 22 days ago | Handshake completed | 1.68 s |
| 24 days ago | Handshake completed | 304 ms |
| 26 days ago | Handshake completed | 519 ms |
| 28 days ago | Handshake completed | 267 ms |
| 29 days ago | Handshake completed | 286 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 com.keywordise/keywordise and makes no claim about it beyond what these checks measured.