mcp

warnings

mcp.secdim.com

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

https://mcp.secdim.com/mcpNo authMCP 2025-11-25v1.27.2last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 267 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 7 tools listable
Credentials demanded in prose	✕get_learn_topic These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 7 tools listed anonymously say in their own descriptions that they need an account or a key (get_learn_topic), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

fetchget_learn_courseget_learn_topicget_secdim_profilesearchsearch_learn_coursessearch_play_challenges

Contract history

24 Aug 2026v1.27.2first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/com-secdim-mcp/badge.svg)](https://mcpi.app/servers/com-secdim-mcp)