Skip to main content
Glama

Related Servers

Alternatives to botgathering-recipes

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      A lightweight Node.js MCP server with zero dependencies offering 9 built-in tools for system info, web fetching, GitHub search, file operations, shell execution, and key-value memory, enabling AI agents to perform these tasks via the Model Context Protocol.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Dynamic MCP server for Node.js enabling runtime tool creation, management, and execution in isolated sandboxes (Docker or Node).
      8
      4 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      A basic MCP server implementation using Node.js and TypeScript that bridges AI models with external tools and data sources via JSON-RPC.
      2
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-extending MCP server that enables AI agents to browse the web, execute shell and Node snippets, automate browser workflows, access files and git, communicate with other agents, and use dozens of domain-specific calculation and research tools.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Code-mode MCP server (docs_search + execute_code two-tool surface) backed by a unified capability manifest across three sandbox kernels (in-process node:vm, WASM via QuickJS / Pyodide / Wasmtime, and remote microVM via E2B / Cloudflare Sandbox). At N=30 tools the bootstrap-context cost drops to 13.6% of direct tool-use. Apache-2.0.
      2
      7
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation3/5

    Descriptions work hard to distinguish tools (e.g. ask_how_to vs search_recipes, get_recipe vs get_recipe_details vs download_recipe), but there are genuinely overlapping clusters: three reading tools and two outcome-reporting tools (quick_report vs report_result). Boundaries exist but require careful reading of long descriptions to select correctly.

    Naming Consistency4/5

    Mostly consistent verb_noun snake_case (get_recipe, report_result, list_categories, register_bot, download_recipe, search_recipes). A few deviations (quick_report, ask_how_to, whoami) are readable but break the strict pattern.

    Tool Count5/5

    Ten tools cleanly cover the recipe lifecycle from discovery through account management and reporting. Each tool earns its place without padding.

    Completeness4/5

    Full consumer-side lifecycle is covered: discovery, reading, downloading, reporting, and account management. Minor gaps like commenting on proposals or editing authored recipes, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues