Remote MCP · Endpoint
Wadifa Info: Morocco Public Jobs MCP server
No. Wadifa Info: Morocco Public Jobs answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://www.wadifa-info.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.wadifa-info.www/morocco-public-jobs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 226 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Moroccan public-sector jobs: open recruitment exams, past papers, salaries, holidays.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 226 ms |
| 4 days ago | Handshake completed | 508 ms |
| 14 days ago | Handshake completed | 483 ms |
| 15 days ago | Handshake completed | 520 ms |
| 15 days ago | Handshake completed | 641 ms |
| 17 days ago | Handshake completed | 355 ms |
| 18 days ago | Handshake completed | 157 ms |
| 19 days ago | Handshake completed | 149 ms |
| 20 days ago | Handshake completed | 154 ms |
| 21 days ago | Handshake completed | 146 ms |
| 23 days ago | Handshake completed | 574 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 Wadifa Info: Morocco Public Jobs and makes no claim about it beyond what these checks measured.