Skip to main content
Glama
tastenkasperle

Strest MCP

by tastenkasperle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Strest MCP

No user-submitted related servers found.

    Related Servers

    • Universal API Connector MCP

      TeodorMCP
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to connect to any API by loading OpenAPI, GraphQL, gRPC, or SOAP specs, with a built-in catalog of 2500+ public APIs, supporting secure execution, response filtering, chaining, and parallel calls.
      34 PyPI
      4
      MIT
    • OutcomeCI MCP Server by outcomeci

      OutcomeCI MCP Serverofficial

      outcomeci
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create, validate, and manage agent-powered workflows across team tools, with tools for inspecting schemas, configuring triggers, and reviewing runs and logs. It provides authorized remote access through OAuth without local installation or shared API keys.
      1
      MIT

    • Stepgate

      Chaarangan
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to run gated, API-only YAML stepfiles in order on the client's own model, making each step's output satisfy schemas, predicates, or HTTP verifiers before proceeding. It also handles API calls, credentials, retries, and hash-chained run records.
      13
      Apache 2.0

    • service-test-mcp

      ohankay
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to test WCF/SOAP and REST services directly, with WSDL discovery, authenticated calls, and deterministic assertions. Supports YAML multi-step scenarios with variable extraction, JSONPath/JSON Schema checks, and CI runs without spawning PowerShell or curl.
      12
      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 an existing scenario, while the other generates a template. There is no meaningful overlap or risk of misselection.

    Naming Consistency3/5

    Both tools share the strest_ prefix, but only strest_run_scenario follows a clear verb_noun pattern. strest_template is noun-based and breaks the convention, making the naming mixed though still readable.

    Tool Count3/5

    Two tools is borderline thin for a scenario-execution server. The core actions are covered, but the surface feels minimal and could benefit from validation or inspection helpers.

    Completeness3/5

    Running a scenario and generating a template cover the primary workflow, but there is no tool for validating scenarios, listing available scenarios, or inspecting execution details. These gaps may force agents to rely on trial-and-error.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources