Skip to main content
Glama
QWED-AI

QWED-MCP

Official
by QWED-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to QWED-MCP

No user-submitted related servers found.

    Related Servers

    • CSL-Core

      Chimera-Protocol
      A
      license
      A
      quality
      A
      maintenance
      Deterministic AI safety policy engine with Z3 formal verification. Write, verify, simulate, and enforce machine-verifiable safety constraints for AI agents. Completely outside the LLM.
      6
      22 PyPI
      17
      Apache 2.0

    • Python Sandbox MCP Server

      Ajaja
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to execute Python code in a restricted sandbox for calculations and data analysis, without giving them a real shell.
      -

    • SymPy Sandbox MCP

      Eis4TY
      A
      license
      A
      quality
      D
      maintenance
      A secure mathematical computation sandbox that enables LLMs to perform symbolic math operations like algebra, calculus, and equation solving via SymPy. It features low-latency execution through pre-warmed process pools and provides standardized JSON outputs for reliable agent integration.
      1
      2
      MIT

    • Touchstone MCP Server

      savecharlie
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides deterministic, verifiable text/code/measurement utilities for AI agents, enabling tasks like unit conversion, citation formatting, diffing, proofreading, readability scoring, and syntax checking with re-executable proof.
      MIT

    • py-sandbox

      LostSyscall
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to execute arbitrary Python code securely in a sandboxed environment with resource limits and security constraints via MCP protocol.
      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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one executes Python code, the other checks the status of a background task. There is no overlap in functionality.

    Naming Consistency4/5

    Both tools use snake_case, but one follows a verb_noun pattern (execute_python_code) while the other is noun_noun (verification_status). Slight inconsistency but still readable.

    Tool Count2/5

    With only 2 tools, the server feels very sparse for any meaningful functionality. A code execution server would typically need more tools for environment management, file I/O, etc.

    Completeness2/5

    The tool set lacks essential operations for a code execution server, such as managing environments, reading files, or handling dependencies. Only bare minimum provided.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources