CTFd MCP Server
Related Servers
Alternatives to CTFd MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA standalone MCP server that connects an agent to any CTFd-based CTF, letting it browse and read challenges, download challenge files, submit flags, unlock hints, and watch the live scoreboard. When the ctfd-whale plugin is present, it also starts, lists, and stops per-team dynamic instances and fetches files from them.121MIT
- FlicenseBqualityDmaintenanceA lightweight MCP server that enables AI assistants to interact with the local machine through terminal, filesystem, and Python execution tools.91-
- AlicenseNot gradedqualityCmaintenanceA fast, lightweight MCP server implementation for building and running custom AI tools with seamless integration.14 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI clients to a Linux terminal for real-time automated penetration testing and CTF challenge solving. It enables AI models to execute terminal commands and interact with offensive security tools like Nmap, SQLMap, and Gobuster.-
- FlicenseNot gradedqualityDmaintenanceOfficial MCP server for the CyberEdu CTF platform that automatically discovers and exposes all CyberEduClient methods as tools, enabling seamless interaction with the platform through MCP-compatible clients.8-
- FlicenseNot gradedqualityDmaintenanceA vulnerable MCP server designed for educational CTF challenges. It demonstrates various MCP security vulnerabilities in a controlled environment.8-
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, but the authentication group (set_token, set_cookie, login, auth_status) plus health overlap around session/state checking, and challenge vs challenges differ only by singular/plural which can cause misselection. Descriptions do help disambiguate the intended usage.
A mix of conventions: verb_noun tools (set_token, submit_flag, download_file, unlock_hint) coexist with bare-noun tools (challenges, challenge, scoreboard, progress, instance_info, health). Each name is readable in isolation, but there is no single predictable pattern.
14 tools is well within a healthy range and each earns its place, covering setup, auth, challenge interaction, and status without bloat.
For a player-facing CTFd client the surface is strong: auth, listing/reading challenges, flag submission, file download, hint unlock, scoreboard, and progress. Minor gaps remain (e.g. category listing, team/teammate endpoints), but core workflows have no dead ends.