Is the Lazymac2x Agent Workflow Engine MCP server down?

mcp-registry/io.github.lazymac2x/agent-workflow-engine · v1.1.0

healthy
Last checked 2026-10-20 09:44 UTC · handshake 274ms

As of 2026-10-20 09:44 UTC, the Lazymac2x Agent Workflow Engine MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,887
outages (90d)
0
tools
5

Cloudflare Workers MCP server: agent-workflow-engine

Install Lazymac2x Agent Workflow Engine MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lazymac2x-agent-workflow-engine-mcp-serv https://api.lazy-mac.com/agent-workflow-engine/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lazymac2x-agent-workflow-engine-mcp-serv": {
      "type": "http",
      "url": "https://api.lazy-mac.com/agent-workflow-engine/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 4 warning(s) across 5 tool(s); ~795 tokens of tool definitions.
Scores higher than 5% of 15,392 MCP servers Glimind has audited.
Its tool list costs an agent ~795 tokens per session — lighter than 80% of servers.
70 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions62
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: auto_route_next_step, create_workflow, get_workflow_status, set_conditional_branch, track_agent_state

2 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: set_conditional_branch, track_agent_state

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_workflow, set_conditional_branch

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine/fixes

create_workflow 1 change
{
  "name": "create_workflow",
  "description": "Create a new multi-agent workflow. Returns a workflow_token encoding the full state — pass it to all subsequent calls.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name",
      "agents"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Workflow name"
      },
      "steps": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Ordered step sequence (agent IDs)"
      },
      "agents": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Agent IDs in this workflow"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
get_workflow_status 1 change
{
  "name": "get_workflow_status",
  "description": "Decode a workflow_token and return full status summary.",
  "inputSchema": {
    "type": "object",
    "required": [
      "workflow_token"
    ],
    "properties": {
      "workflow_token": {
        "type": "string",
        "description": "Token encoding workflow state"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
set_conditional_branch 1 change
{
  "name": "set_conditional_branch",
  "description": "Attach a conditional branch to a step. Operator is evaluated against agent output when routing. Returns updated workflow_token.",
  "inputSchema": {
    "type": "object",
    "required": [
      "workflow_token",
      "step_index",
      "condition_logic"
    ],
    "properties": {
      "step_index": {
        "type": "integer",
        "description": "Step index to attach condition to"
      },
      "workflow_token": {
        "type": "string",
        "description": "Current workflow token"
      },
      "condition_logic": {
        "type": "object",
        "required": [
          "operator",
          "true_agent"
        ],
        "properties": {
          "field": {
            "type": "string",
            "example": "success",
            "description": "Output field to evaluate"
          },
          "value": {
            "description": "Comparison value for equals/gte/lte/contains operators"
          },
          "operator": {
            "enum": [
              "equals",
              "not_equals",
              "truthy",
              "falsy",
              "gte",
              "lte",
              "contains"
            ],
            "type": "string"
          },
          "true_agent": {
            "type": "string",
            "description": "Agent ID if condition is true"
          },
          "description": {
            "type": "string",
            "description": "Human-readable description"
          },
          "false_agent": {
            "type": "string",
            "description": "Agent ID if condition is false"
          }
        }
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lazymac2x/agent-workflow-engine"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/agent-workflow-engine"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fagent-workflow-engine?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:844a28a6500c171c…, first seen 2026-10-17, included at leaf 11025 of 32,155. Version history · verify what your client received.

Tools (5)

Compare: most reliable devops servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lazymac2x Agent Workflow Engine MCP server down right now?

As of 2026-10-20 09:44 UTC, the Lazymac2x Agent Workflow Engine MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Lazymac2x Agent Workflow Engine MCP server provide?

Lazymac2x Agent Workflow Engine MCP server advertises 5 tools, including auto_route_next_step, create_workflow, get_workflow_status, set_conditional_branch, track_agent_state.

How do I install Lazymac2x Agent Workflow Engine MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/agent-workflow-engine/mcp

Is the Lazymac2x Agent Workflow Engine MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lazymac2x Agent Workflow Engine MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve