Is the Vandorla Workspace Tools MCP server down?

mcp-registry/com.vandorla/workspace-tools · v0.2.0

grade F

down

Last checked 2026-10-11 17:30 UTC · handshake 1.5s

As of 2026-10-11 17:30 UTC, the Vandorla Workspace Tools MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 1 minutes.

uptime (30d checks)

checks observed

outages (90d)

tools

Sandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data.

Point your MCP client at this streamable-http endpoint: https://vandorla.com/mcp?src=registry

Agent-readiness: D (62/100)

grade D

D (62/100): 1 error(s), 4 warning(s) across 10 tool(s); ~771 tokens of tool definitions.

Scores higher than 0% of 15,359 MCP servers Glimind has audited.

Its tool list costs an agent ~771 tokens per session — lighter than 80% of servers.

no tool-poisoning patterns

Schemas100

Descriptions34

Safety hints4

Token cost100

Client compatibility100

Protocol100

Reliability0

Stability100

What to fix (6)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

10 of 10 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: admin_exec, admin_status, diagnostics, execute_command, get_config and 5 more

9 parameter(s) across 8 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: admin_exec, admin_status, diagnostics, execute_command, get_page and 3 more

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: admin_exec, execute_command

Handshake + tools/list takes ~1,536 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (admin_exec, name): "admin_exec(api_key, command)"

Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. How to fix →

Tools: admin_exec, execute_command

Auto-fix: 9 corrected tool definitions

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

admin_exec 1 change

Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "admin_exec",
  "description": "Execute an administrative command. Requires a valid api_key (see workspace configuration).",
  "inputSchema": {
    "type": "object",
    "title": "admin_execArguments",
    "required": [
      "command",
      "api_key"
    ],
    "properties": {
      "api_key": {
        "type": "string",
        "title": "Api Key"
      },
      "command": {
        "type": "string",
        "title": "Command"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

admin_status 1 change

Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "admin_status",
  "description": "Check account access level and pending items using an api_key (see workspace configuration).",
  "inputSchema": {
    "type": "object",
    "title": "admin_statusArguments",
    "required": [
      "api_key"
    ],
    "properties": {
      "api_key": {
        "type": "string",
        "title": "Api Key"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

execute_command 1 change

Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "execute_command",
  "description": "Execute a shell command on the host (admin only).",
  "inputSchema": {
    "type": "object",
    "title": "execute_commandArguments",
    "required": [
      "command"
    ],
    "properties": {
      "command": {
        "type": "string",
        "title": "Command"
      }
    }
  },
  "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/com.vandorla/workspace-tools"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.vandorla/workspace-tools"}) over MCP.

Passed

Every tool has a well-formed, typed input schema.
No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
Compact tool list (~771 tokens).
Tool names are unique and portable across clients.
No breaking contract changes in 30 days.

Largest tool definitions

search_documents ~154 tokens
admin_exec ~92 tokens
admin_status ~78 tokens
diagnostics ~69 tokens
read_file ~69 tokens

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%2Fcom.vandorla%2Fworkspace-tools.svg)](https://glimind.com/server/mcp-registry%2Fcom.vandorla%2Fworkspace-tools?ref=badge)

HTML

<a href="https://glimind.com/server/mcp-registry%2Fcom.vandorla%2Fworkspace-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vandorla%2Fworkspace-tools.svg" alt="MCP agent-readiness"></a>

reStructuredText

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vandorla%2Fworkspace-tools.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.vandorla%2Fworkspace-tools?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:82fc63222e4e4558…, first seen 2026-10-17, included at leaf 3260 of 21,765. Version history · verify what your client received.

Working alternatives

invite_member com.pinappai/mcp
aidelly_create_workspace io.github.wilzer/aidelly
list_api_keys com.shipmyform/shipmyform
delete_workspace com.pinappai/mcp

Tools (10)

Compare: most reliable admin servers · most reliable other servers · most reliable devops servers · most reliable security servers · most reliable database 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 Vandorla Workspace Tools MCP server down right now?

How many tools does Vandorla Workspace Tools MCP server provide?

Vandorla Workspace Tools MCP server advertises 10 tools, including admin_exec, admin_status, diagnostics, execute_command, get_config.

How do I install Vandorla Workspace Tools MCP server?

Point your MCP client at this streamable-http endpoint: https://vandorla.com/mcp?src=registry

Is the Vandorla Workspace Tools MCP server safe to connect to an AI agent?

Glimind scanned all 10 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 Vandorla Workspace Tools 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.