Remote MCP · Endpoint

Dice MCP MCP server

No. Dice MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.dice.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.DiceHoldingsInc/dice-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
338 ms
Tools exposed
3 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
Dice MCP: Search for tech jobs on Dice.com
Listing
From the official MCP registry (active).
Recent checks of Dice MCP
CheckedResultHandshake
1 hour agoHandshake completed338 ms
1 day agoHandshake completed27 ms
3 days agoHandshake completed315 ms
3 days agoFailed - the request timed out—
4 days agoHandshake completed343 ms
5 days agoHandshake completed37 ms
7 days agoFailed - the request timed out—
10 days agoHandshake completed781 ms
12 days agoHandshake completed39 ms
15 days agoHandshake completed35 ms
17 days agoHandshake completed27 ms
19 days agoHandshake completed26 ms
21 days agoHandshake completed38 ms
23 days agoHandshake completed22 ms
25 days agoHandshake completed20 ms
26 days agoHandshake completed31 ms
28 days agoHandshake completed55 ms
29 days agoHandshake completed22 ms

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

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 Dice MCP and makes no claim about it beyond what these checks measured.