Skip to main content
Glama
medianemi-beep

Soma MCP Server

by medianemi-beep
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Soma MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-testbed

      anthonys1760
      A
      license
      A
      quality
      C
      maintenance
      Provides an isolated workspace for testing candidate code, runs tests, and returns deterministic pass/fail verdicts. Enables automated grading of software engineering solutions by ensuring reproducible test runs.
      5
      MIT

    • OmniBridge MCP Server

      SyedDaiam9101
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides isolated sandbox environments for AI agents to execute code securely, generating signed receipts for every execution to ensure auditability and trust.
      61 npm
      4
      MIT

    • Netmind Code Interpreter

      protagolabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure cloud-based execution of code across 14+ programming languages within a sandboxed environment. It supports file management, standard input/output handling, and automatic generation of visual artifacts like plots and charts.
      MIT

    • verdict

      Dgotlieb
      A
      license
      A
      quality
      B
      maintenance
      Provides structured, sandboxed test and lint feedback for coding agents, returning compact typed verdicts with failure fingerprints instead of raw runner output. It enables impact-selected test execution in isolated containers, distinguishing pre-existing failures from regressions.
      4
      Apache 2.0
    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

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one verifies provided code, the other generates code with verification. There is no overlap or confusion between them.

    Naming Consistency5/5

    Both tools follow the identical pattern of 'soma_' prefix plus a verb_noun structure: verify_code and generate_verified_code. Naming is uniform and predictable.

    Tool Count3/5

    With only 2 tools, the server is minimal but focused on a narrow purpose. While the count feels thin for a general toolkit, it is reasonable for a specialized verification service. It sits at the borderline.

    Completeness4/5

    The server covers the core workflows of code verification and generation with verification. Minor gaps exist, such as no ability to fetch or check certificate details after generation, but the primary lifecycle is covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources