Remote MCP · Endpoint
com.easyonward/mcp-server MCP server
No. com.easyonward/mcp-server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.easyonward.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.easyonward/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 415 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Passport visa, entry & transit requirements for any country pair, with official government sources.
- Repository
- https://github.com/EasyOnward/mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 415 ms |
| 18 hours ago | Handshake completed | 412 ms |
| 2 days ago | Handshake completed | 421 ms |
| 3 days ago | Handshake completed | 421 ms |
| 4 days ago | Handshake completed | 428 ms |
| 5 days ago | Handshake completed | 532 ms |
| 6 days ago | Handshake completed | 419 ms |
| 7 days ago | Handshake completed | 391 ms |
| 10 days ago | Handshake completed | 441 ms |
| 13 days ago | Handshake completed | 623 ms |
| 15 days ago | Handshake completed | 410 ms |
| 17 days ago | Handshake completed | 406 ms |
| 19 days ago | Handshake completed | 387 ms |
| 21 days ago | Handshake completed | 407 ms |
| 23 days ago | Handshake completed | 406 ms |
| 25 days ago | Handshake completed | 405 ms |
| 27 days ago | Handshake completed | 401 ms |
| 28 days ago | Handshake completed | 414 ms |
| 29 days ago | Handshake completed | 360 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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.easyonward/mcp-server and makes no claim about it beyond what these checks measured.