Skip to main content
Glama

Related Servers

Alternatives to dtc-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes a V8 JavaScript runtime as a tool for AI agents like Claude and Cursor. Supports persistent heap snapshots via S3 or local filesystem, and is ready for integration with modern AI development environments.
      57
      Rust
      AGPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure execution of arbitrary JavaScript code within a sandboxed QuickJS WASM environment, allowing language models or other MCP clients to safely run JavaScript code snippets without compromising the host system.
      4
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that gives AI assistants a secure gVisor-isolated sandbox to run Python or JavaScript code, returning stdout, stderr, and exit codes without local access.
      1
      26 npm
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      A secure JavaScript REPL server that enables executing code snippets in a sandboxed environment with memory protection, timeout handling, and comprehensive error reporting.
      1
      3 npm
      122
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A code-first MCP server that provides a single tool to execute JavaScript or TypeScript with authenticated access to Google Workspace APIs. It enables flexible interactions with services like Calendar and Drive by running user-provided scripts through a built-in runtime environment.
      1
      7
      -
    • A
      license
      B
      quality
      D
      maintenance
      A secure Model Context Protocol server that allows AI assistants and LLM applications to safely execute Python and JavaScript code snippets in containerized environments.
      2
      204
      MIT

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools occupy clearly distinct roles: execute_code runs sandboxed code, while search_docs finds relevant documentation and read_doc fetches a specific doc chunk. Even though search_docs and read_doc both access documentation, their boundaries are explicit: search for exploration, read for deterministic retrieval by path.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun snake_case pattern: execute_code, search_docs, read_doc. This makes the tool's action and target immediately predictable.

    Tool Count5/5

    Three tools are well-scoped for this server's purpose: one for code execution and two complementary docs-access tools. Each tool earnts its place and there is no bloat or redundancy.

    Completeness5/5

    The server covers its apparent lifecycle completely: discover what is available via read_doc/search_docs, then execute code against the constrained SDK with persistent globalThis state. There are no obvious dead ends or missing operations that would block an agent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues