Skip to main content
Glama

⚑ Strest MCP (Strest Orchestrator)

License: MIT Glama Score MCP Compatible Tests Security Guard Zero Dependencies

Headless Declarative Multi-Step REST API Test & Chaining Engine for Autonomous AI Agents and DevSecOps.
Execute complex, multi-stage API workflows (Auth βž” Token Extraction βž” Resource Creation βž” Assertions) in a single deterministic MCP tool call.


πŸ’‘ The Problem

Autonomous AI agents (Claude Code, Cursor, Antigravity, AutoGen, CrewAI) and CI pipelines frequently need to interact with multi-step REST APIs.
When executing chained requests step-by-step with individual curl commands:

  1. Context Window Waste & Token Bloat: Passing whole JSON payloads back and forth across multiple LLM turns wastes hundreds of tokens.

  2. Fragile State Propagation: Extracting tokens, session IDs, and foreign keys across separate prompts introduces hallucinations and state loss.

  3. SSRF & Security Hazards: AI agents given raw network access can be coerced into probing internal cloud metadata endpoints (169.254.169.254).

Strest MCP solves this: You pass a declarative multi-step scenario definition to the engine. It executes all steps sequentially with in-memory variable chaining, enforces strict assertions, applies active SSRF defense, and returns a clean, structured execution report in a single round-trip.


Related MCP server: AGENTIQ

⚑ Key Capabilities

  • πŸ”— Declarative Multi-Step Chaining: Chain outputs from previous steps into downstream headers, query params, or JSON bodies using <$ steps.<step_name>.body.<property> $>.

  • πŸ›‘οΈ Built-in SSRF & Cloud Metadata Shield: Proactively blocks attacks against AWS/GCP/Azure instance metadata endpoints (169.254.169.254, metadata.google.internal), local loopbacks, and dangerous protocols (file://, ftp://).

  • πŸͺΆ Zero External Dependencies: Built entirely with native Node.js 20+ fetch, keeping the package footprint lightweight and lightning-fast.

  • πŸ€– Model Context Protocol (MCP) Native: Integrates seamlessly via stdio JSON-RPC 2.0 with Claude Desktop, Cursor, Antigravity, and any MCP-compliant client.

  • 🎯 Rich Assertions: Status code validation, regex header checks, deep JSON body assertions, and timing thresholds.


πŸ€– Model Context Protocol (MCP) Setup

Add to Claude Desktop / Cursor / Antigravity

Add the following to your claude_desktop_config.json or MCP settings:

{
  "mcpServers": {
    "strest-mcp": {
      "command": "npx",
      "args": ["-y", "strest-mcp"]
    }
  }
}

Or run directly from a local clone:

{
  "mcpServers": {
    "strest-mcp": {
      "command": "node",
      "args": ["/path/to/strest_orchestrator/src/mcp/server.mjs"]
    }
  }
}

Available MCP Tools

Tool

Description

Input Parameters

strest_run_scenario

Executes a declarative multi-step REST API workflow scenario with automatic variable chaining and schema assertions.

scenario (object) OR scenarioPath (string)

strest_template

Generates a ready-to-use template for multi-step authentication and CRUD chaining.

baseUrl (optional string, e.g. http://localhost:5000)


πŸ’» CLI Usage

You can also run Strest Orchestrator as a standalone CLI tool:

# Display help and usage
npx strest help

# Run an API workflow scenario from a JSON file
npx strest run scenarios/auth_and_crud.json

# Generate a starter template
npx strest template > scenario.json

πŸ“‹ Scenario Example (Chaining in Action)

{
  "name": "Auth and User Project Creation",
  "steps": [
    {
      "name": "login",
      "url": "https://api.example.com/v1/auth/login",
      "method": "POST",
      "headers": { "Content-Type": "application/json" },
      "body": { "username": "admin", "password": "SuperSecretPassword" },
      "assert": {
        "status": 200,
        "body": { "token": "defined" }
      }
    },
    {
      "name": "create_project",
      "url": "https://api.example.com/v1/projects",
      "method": "POST",
      "headers": {
        "Content-Type": "application/json",
        "Authorization": "Bearer <$ steps.login.body.token $>"
      },
      "body": {
        "title": "Autonomous Agent Workspace",
        "requestId": "<$ faker.uuid $>"
      },
      "assert": {
        "status": 201,
        "body": { "id": "defined" }
      }
    }
  ]
}

πŸ›‘οΈ Security & Hardening (Raptor Guard v2.0)

  • SSRF Prevention: Blocks requests to IPv4/IPv6 link-local addresses, link-local multicast, and known cloud metadata IP ranges (169.254.169.254, 100.100.100.200).

  • Path Traversal Shield: Resolves and validates scenario file paths against path traversal sequences (../, null bytes, system files).

  • Hermetic Execution: 100% offline self-testing suite with embedded ephemeral mock servers.


πŸ“œ Origin & Credits

  • Based on the concept of eykrehbein/strest (1.7k+ ⭐, MIT).

  • Modernized, decoupled, SSRF-hardened, and transformed into an autonomous Model Context Protocol server by Christopher Hailfinger (@tastenkasperle) as part of the Diamantenschmiede initiative.


πŸ“„ License

MIT License β€” see LICENSE for details.

Available Tools

2 tools
strest_run_scenarioB

Executes a declarative multi-step REST API workflow scenario with automatic variable chaining and schema assertions.

Inputs: scenario, scenarioPath.

strest_templateB

Generates a ready-to-use template for multi-step authentication and CRUD chaining.

Inputs: baseUrl.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • 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.
      52 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      15
      Apache 2.0
    • 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