Remote MCP · Endpoint

com.sourcerdesk/sourcers-desk MCP server

No. com.sourcerdesk/sourcers-desk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sourcerdesk.com/mcp

The last check completed an MCP handshake.

Registry name
com.sourcerdesk/sourcers-desk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Recruiter-grade boolean/x-ray search strings from a 20-year sourcing playbook.
Website
https://sourcerdesk.com/
Repository
https://github.com/glennquinting/sourcerdesk-api-docs
Listing
From the official MCP registry (active).
Recent checks of com.sourcerdesk/sourcers-desk
CheckedResultHandshake
1 hour agoHandshake completed56 ms
2 days agoHandshake completed56 ms
4 days agoHandshake completed54 ms
6 days agoHandshake completed50 ms
7 days agoHandshake completed67 ms
9 days agoHandshake completed58 ms
10 days agoHandshake completed55 ms
11 days agoHandshake completed52 ms
14 days agoHandshake completed62 ms
15 days agoHandshake completed49 ms
17 days agoHandshake completed137 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed52 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed52 ms
22 days agoHandshake completed56 ms
23 days agoHandshake completed53 ms
24 days agoHandshake completed52 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.sourcerdesk/sourcers-desk and makes no claim about it beyond what these checks measured.