Remote MCP · Endpoint

Dice MCP MCP server

No. Dice MCP answered an MCP handshake 5 hours ago.

UpLast checked 5 hours 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
38 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 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
5 hours agoHandshake completed38 ms
2 days agoHandshake completed22 ms
4 days agoHandshake completed20 ms
5 days agoHandshake completed31 ms
7 days agoHandshake completed55 ms
8 days agoHandshake completed22 ms
9 days agoHandshake completed30 ms
12 days agoHandshake completed32 ms
13 days agoHandshake completed410 ms
15 days agoHandshake completed31 ms
16 days agoHandshake completed30 ms
17 days agoHandshake completed23 ms
19 days agoHandshake completed21 ms
19 days agoHandshake completed24 ms
20 days agoHandshake completed371 ms
21 days agoHandshake completed88 ms
22 days agoHandshake completed334 ms

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

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.