MCP server for CTFd v3: list challenges, submit flags, and query scoreboards via AI agents.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
CTFD_ADMIN_TOKENAPI keyoptionalCTFd API access token (preferred authentication method)
CTFD_SESSION_COOKIEAPI keyoptionalFull CTFd session cookie, e.g. session=abc...
CTFD_PASSWORDAPI keyoptionalPassword for CTFd form login
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server for CTFd v3: list challenges, submit flags, and query scoreboards via AI agents.
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.