Is the WebArm24 MCP server down?

mcp-registry/online.webarm24/webarm24 · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:56 UTC · handshake 668ms

As of 2026-11-22 16:56 UTC, the WebArm24 MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
688
outages (90d)
1
tools
93

AI automation platform (n8n/Zapier alternative): build, schedule and run workflows from your agent.

Point your MCP client at this streamable-http endpoint: https://webarm24.online/mcp

Agent-readiness: D (59/100)

D (59/100): 0 error(s), 6 warning(s) across 93 tool(s); ~10,130 tokens of tool definitions.
Scores higher than 0% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~10,130 tokens per session — more than 85% of servers.
59 → 59 since 2026-11-17
no tool-poisoning patterns
Descriptions18
Safety hints0
Schemas89
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (7)

93 of 93 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: account_me, agent_job_get, agent_job_list, agent_job_submit, ai_models_list and 88 more

93 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

185 parameter(s) across 79 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: agent_job_get, agent_job_list, agent_job_submit, analyze_json, browser_click and 74 more

32 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: agent_job_submit, pipeline_create, pipeline_delete, pipeline_deleted_restore, pipeline_group_create and 27 more

5 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: agent_job_list, skill_delete, storage_delete, storage_files_list, storage_read

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: storage_write

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: 84 corrected tool definitions

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

agent_job_get 1 change
{
  "name": "agent_job_get",
  "description": "Job status/result (queued|running|completed|failed).",
  "inputSchema": {
    "type": "object",
    "title": "agent_job_getArguments",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "title": "Job Id"
      },
      "structured_data_only": {
        "type": "boolean",
        "title": "Structured Data Only",
        "default": false
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
agent_job_list 1 change
{
  "name": "agent_job_list",
  "description": "Recent agent jobs.",
  "inputSchema": {
    "type": "object",
    "title": "agent_job_listArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 20
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
agent_job_submit 1 change
{
  "name": "agent_job_submit",
  "description": "Run the browsing agent on a task (async; costs agent_job credits). Jobs are in-memory (lost on restart).",
  "inputSchema": {
    "type": "object",
    "title": "agent_job_submitArguments",
    "required": [
      "text"
    ],
    "properties": {
      "lang": {
        "type": "string",
        "title": "Lang",
        "default": "en"
      },
      "text": {
        "type": "string",
        "title": "Text"
      },
      "variables": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": true
          },
          {
            "type": "null"
          }
        ],
        "title": "Variables",
        "default": null
      },
      "target_url": {
        "type": "string",
        "title": "Target Url",
        "default": "__agent__"
      },
      "output_json_schema": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Output Json Schema",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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/online.webarm24/webarm24"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/online.webarm24/webarm24"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fonline.webarm24%2Fwebarm24.svg)](https://glimind.com/server/mcp-registry%2Fonline.webarm24%2Fwebarm24?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fonline.webarm24%2Fwebarm24?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fonline.webarm24%2Fwebarm24.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:52fc52dd4065106f…, first seen 2026-11-17, included at leaf 319237 of 384,654. Version history · verify what your client received.

Tools (93)

Compare: most reliable other servers · most reliable browser servers · most reliable devops servers · most reliable ml servers · most reliable payments 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the WebArm24 MCP server down right now?

As of 2026-11-22 16:56 UTC, the WebArm24 MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does WebArm24 MCP server provide?

WebArm24 MCP server advertises 93 tools, including account_me, agent_job_get, agent_job_list, agent_job_submit, ai_models_list.

How do I install WebArm24 MCP server?

Point your MCP client at this streamable-http endpoint: https://webarm24.online/mcp

Is the WebArm24 MCP server safe to connect to an AI agent?

Glimind scanned all 93 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 WebArm24 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