Skip to content
External endpointresponds

mcp

Personalised developer security learning pathways from SecDim's challenges and courses.

Endpoint URL
https://mcp.secdim.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
492 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.secdim/mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
SecDim MCP
Version
1.27.2
Capability keys
experimental, prompts, resources, tools
Tool names
get_secdim_profile, search_play_challenges, search, fetch, search_learn_courses, get_learn_course, get_learn_topic
Instructions excerpt

SecDim MCP server gives access to two complementary SecDim products: - SecDim Play: hands-on secure coding, appsec, devsecops, ai security and web3 security challenges (labs) where developers find and fix real vulnerabilities and earn score/points. - SecDim Learn: tutorial-based courses (text, video and hands-on lab topics) on secure coding, secure design, devsecops, cloud security and more, often complementary or prerequisite to SecDim Play challenges. To build a personalized learning pathway: 1. Ask the user 4 brief questions: languages/frameworks they use daily, their role (backend/frontend/DevOps/etc.), what they want to achieve (verify AI generated fixes, fix a specific vulnerability, OWASP Top 10 coverage, certification prep, etc.) and how much time per week they can dedicate to learning (1, 2-4 hours per week, 1-2 days). 2. If they have a SecDim account, call get_secdim_profile to see their actual challenge history and demonstrated skill level. Weight demonstr

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 399ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 406ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 542ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 492ms