Skip to main content
Glama
ballz4z4

FlagForge MCP Server

by ballz4z4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to FlagForge MCP Server

No user-submitted related servers found.

    Related Servers

    • CTFd MCP Server

      umbra2728
      A
      license
      B
      quality
      C
      maintenance
      Enables interaction with CTFd platforms for Capture The Flag competitions, allowing users to list challenges, read details, manage dynamic Docker containers, and submit flags through natural language.
      5
      24
      Apache 2.0

    • attackforge-mcp

      unstrike
      F
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to AttackForge's Self-Service API with full endpoint coverage, response size optimization, and local caching for efficient use in long conversations.
      11
      -

    • forgejo-mcp

      openmanbo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.
      118 npm
      MIT

    • KadeMCP

      orgito1015
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to solve CTF challenges through natural language by disassembling binaries, cracking hashes, fuzzing web applications, extracting steganography, and running pwntools exploits.
      1
      MIT

    • HTB MCP Server

      zebbern
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive live Hack The Box labs through the real HTB Labs API — spawning, resetting and extending machines, submitting user and root flags with difficulty ratings, browsing challenges, and switching or downloading VPN configurations for the authenticated account. Every call hits the live API rather than cached content, with destructive actions annotated so hosts can gate them behind consent.
      22
      366 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool targets a specific resource and action pair: events, challenges, evidence, flags, writeups, artifacts, and knowledge search. The only possible near-overlap between update_challenge and set_challenge_status is resolved by the latter being explicitly scoped to lifecycle status.

    Naming Consistency5/5

    Tool names follow a consistent lowercase snake_case verb_noun pattern throughout, such as list_*, create_*, get_*, update_*, delete_*, save_*, and upload_*. This makes the intended action of each tool predictable and easy to select.

    Tool Count4/5

    At 19 tools, the set is slightly above the typical well-scoped range, but the breadth is justified by the full CTF workflow: events, challenge CRUD, status/locking, evidence, flags, writeups, artifacts, and search. No tools are redundant; each contributes a distinct operation.

    Completeness4/5

    The core challenge lifecycle is well covered with create/read/update/delete plus status, locking, evidence, flags, writeups, and artifacts. Minor gaps exist around event updates/deletes and direct artifact retrieval, but agents can work around these for solving and documentation workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources