Remote MCP · Endpoint

com.secdim/mcp MCP server

No. com.secdim/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.secdim.com/mcp

The last check completed an MCP handshake.

Registry name
com.secdim/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
322 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Personalised developer security learning pathways from SecDim's challenges and courses.
Repository
https://github.com/secdim/mcp
Listing
From the official MCP registry (active).
Recent checks of com.secdim/mcp
CheckedResultHandshake
1 hour agoHandshake completed322 ms
2 days agoHandshake completed348 ms
4 days agoHandshake completed324 ms
6 days agoHandshake completed294 ms
7 days agoHandshake completed306 ms
9 days agoHandshake completed304 ms
10 days agoHandshake completed286 ms
11 days agoHandshake completed305 ms
14 days agoHandshake completed1.56 s
15 days agoHandshake completed284 ms
17 days agoHandshake completed498 ms
18 days agoHandshake completed289 ms
19 days agoHandshake completed285 ms
20 days agoHandshake completed294 ms
21 days agoHandshake completed289 ms
22 days agoHandshake completed283 ms
23 days agoHandshake completed303 ms
24 days agoHandshake completed314 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.secdim/mcp and makes no claim about it beyond what these checks measured.