CTFd
PYPI · CTFD-MCP-SERVER
MCP server for CTFd v3: list challenges, submit flags, and query scoreboards via AI agents.
Available components
Last scanned (18 hours ago)
Scores higher than 92% of PyPI servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 44 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MrJamescot/ctfd-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 45 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 846 tokens (~60/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.63 functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/ctfd-mcp-server@1.0.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MrJamescot/ctfd-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MrJamescot/ctfd-mcp-server/.github/workflows/publish-pypi.yml@refs/tags/v1.0.4 |
| Rekor log index | 2904859233 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3ecd102e812c5855673a09f60fd1b09e6aac1ab4217339e97cdfe24cea1726fe |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 44 packages
| Packages resolved | 44 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
auth_status ~32
Report whether the current session is authenticated and which auth mode is active. Reveals no tokens/cookies/passwords.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
challenge ~60
Get the full detail of a single challenge by numeric id or name. Includes description, category, value, files, hints and connection info. Args: identifier: challenge id (e.g. "3") or challenge name.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
challenges ~116
List challenges with optional filters and pagination. Args: category: filter by challenge category (exact match). search: case-insensitive substring match on challenge name. solved: only show solved (True) or unsolved (False) challenges. page: page number (1-based) when no filters are applied. per_page: number of challenges per page (1-100).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| page | integer | – | – |
| per_page | integer | – | – |
| search | – | – | – |
| solved | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
download_file ~121
Download a challenge attachment to the local machine. Challenge detail (``challenge`` tool) returns a ``files`` array with site-relative paths like ``/files/<hash>/<name>`` (signed URLs on some deployments). Pass one of those values here. Args: file_url: absolute http(s) URL or site-relative path to the file. dest_dir: optional local directory to store the file in (default: CTFD_DOWNLOAD_DIR or ./downloads).
| Name | Type | Req | Description |
|---|---|---|---|
| dest_dir | – | – | – |
| file_url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
health ~24
Perform a health check: CTFd reachability, API status and authentication state.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
instance_info ~26
Return safe, public metadata about the configured CTFd instance. No secrets are included.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
login ~70
Log in to CTFd with a username and password (kept in memory only). Creates a session cookie; the password is never returned. Args: username: CTFd account name. password: CTFd account password.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | – |
| username | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
progress ~18
Return the authenticated user's progress (score and solved challenges).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scoreboard ~18
Return the public CTFd scoreboard (top standings).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_base_url ~54
Configure the CTFd instance this server talks to. Args: url: absolute http(s) URL of the CTFd instance, e.g. https://ctf.example.com
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_cookie ~56
Use a session cookie for authentication (memory only, never logged). Args: cookie: full session cookie value, e.g. "session=abc..." or "name=..; session=..".
| Name | Type | Req | Description |
|---|---|---|---|
| cookie | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_token ~42
Use an API token for authentication (stored in memory only, never logged). Args: token: CTFd API access token.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_flag ~115
Submit a flag for a challenge. Safety: requires confirm=True. Provide exactly one of challenge_id or challenge_name. The flag value is never logged. Args: flag: the flag to submit. challenge_name: name of the challenge to submit against. challenge_id: numeric id of the challenge to submit against. confirm: must be set to True as an explicit submission opt-in.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_id | – | – | – |
| challenge_name | – | – | – |
| confirm | boolean | – | – |
| flag | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
unlock_hint ~94
Unlock a challenge hint and return its content. WARNING: on CTFd a hint with a non-zero ``cost`` deducts that many points from your account. When two hint IDs are needed (e.g. a hint's prerequisites), unlock them in order. Args: hint_id: numeric id of the hint (see the ``challenge`` tool result).
| Name | Type | Req | Description |
|---|---|---|---|
| hint_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the CTFd MCP server?
CTFd runs locally as a PyPI package, launched with uvx ctfd-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ctfd-mcp-server
claude mcp add mrjamescot-ctfd-mcp-server -- uvx ctfd-mcp-server
What is the CTFd MCP server?
CTFd is an MCP server listed in the public MCP registry as io.github.MrJamescot/ctfd-mcp-server. MCP server for CTFd v3: list challenges, submit flags, and query scoreboards via AI agents. This page covers its PyPI package (ctfd-mcp-server).
Is the CTFd MCP server safe to use?
CTFd scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CTFd MCP server expose?
CTFd exposes 14 tools: set_base_url, set_token, set_cookie, login, challenges, and 9 more. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the CTFd MCP server still maintained?
CTFd is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the CTFd MCP server under?
CTFd declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the CTFd MCP server?
VerifyMCP ran 16 checks on CTFd, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.