Remote MCP · Endpoint
ElkassabgiData MCP server
No. ElkassabgiData answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://elkassabgidata-mcp.elkassabgi.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- com.elkassabgidata/elkassabgidata
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 673 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- A growing family of free academic data libraries: finance, economics, and beyond (ElkassabgiData).
- Website
- https://elkassabgidata.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 673 ms |
| 19 hours ago | Handshake completed | 584 ms |
| 2 days ago | Handshake completed | 601 ms |
| 3 days ago | Handshake completed | 589 ms |
| 4 days ago | Handshake completed | 725 ms |
| 5 days ago | Handshake completed | 733 ms |
| 6 days ago | Handshake completed | 571 ms |
| 7 days ago | Handshake completed | 747 ms |
| 10 days ago | Handshake completed | 628 ms |
| 13 days ago | Handshake completed | 1.27 s |
| 15 days ago | Handshake completed | 489 ms |
| 17 days ago | Handshake completed | 609 ms |
| 19 days ago | Handshake completed | 700 ms |
| 21 days ago | Handshake completed | 810 ms |
| 23 days ago | Handshake completed | 828 ms |
| 25 days ago | Handshake completed | 517 ms |
| 27 days ago | Handshake completed | 679 ms |
| 28 days ago | Handshake completed | 367 ms |
| 29 days ago | Handshake completed | 863 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 ElkassabgiData and makes no claim about it beyond what these checks measured.