Is the XGuard MCP server down?

mcp-registry/io.github.moelayyan90/xguard · registry v6.1.0 · server reports v6.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
degraded
Last checked 2026-11-22 17:57 UTC · handshake 252ms

As of 2026-11-22 17:57 UTC, the XGuard MCP server is degraded with a Glimind reliability score of 59/100 (grade D). Over the last 30 days it answered 73.8% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
73.8%
checks observed
3,979
outages (90d)
3
tools
53

Bounded digital tasks, simple checkout, private result recovery and signed receipts.

Point your MCP client at this streamable-http endpoint: https://xguardgate.com/mcp

Agent-readiness: F (50/100)

F (50/100): 1 error(s), 7 warning(s) across 53 tool(s); ~25,318 tokens of tool definitions.
Scores higher than 0% of 27,661 MCP servers Glimind has audited.
Its tool list costs an agent ~25,318 tokens per session — more than 95% of servers.
68 → 50 since 2026-11-04
no tool-poisoning patterns
Descriptions40
Safety hints79
Schemas100
Protocol100
Stability20
Token cost22
Reliability20
Client compatibility28

What to fix (10)

Up 60.3% of the time over the last 30 days; median recovery 5 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

3 tool definition(s) exceed ~1,200 tokens each (largest: xguard.preflight, ~5,083).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~12,066 tokens every session. How to fix →

Tools: xguard.preflight, xguard.pricing.quote, xguard.web.fetch · saves ~12,066 tokens/session

53 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 →

166 parameter(s) across 38 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: execute_gpu_job, execute_inference, get_execution_receipt, quote_gpu_job, quote_inference and 33 more

34 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: xguard.action.catalog, xguard.action.quote, xguard.action.result, xguard.authority.catalog, xguard.authority.command and 29 more

7 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: xguard_compare_suppliers, xguard_create_deal, xguard_purchase_service, xguard_request_quote, xguard_verify_payment and 2 more

Loading this server's tool list costs an agent ~25,318 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

In the last 30 days: 8 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. 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 →

Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (execute_gpu_job, name): "execute_gpu_job(image, input, payer, region)"

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

Tools: execute_gpu_job

Auto-fix: 34 corrected tool definitions

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

xguard.action.catalog 1 change
{
  "name": "xguard_action_catalog",
  "description": "List bounded Action Cloud services, final card prices, checkout URLs and actual PayPal activation blockers. No payment or execution.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "idempotentHint": true
  },
  "title": "Review task prices and PayPal availability"
}
xguard.action.quote 1 change
{
  "name": "xguard_action_quote",
  "description": "Validate task input and review its final USD price without payment or external execution. Human approval takes place at the shared checkout.",
  "inputSchema": {
    "type": "object",
    "required": [
      "service",
      "input"
    ],
    "properties": {
      "input": {
        "type": "object"
      },
      "service": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "idempotentHint": true
  },
  "title": "Review a digital task price in USD"
}
xguard.action.result 1 change
{
  "name": "xguard_action_result",
  "description": "Recover the original paid result and signed receipt with its private recovery key. Never creates or charges another order.",
  "inputSchema": {
    "type": "object",
    "required": [
      "order_id",
      "recovery_token"
    ],
    "properties": {
      "order_id": {
        "type": "string",
        "pattern": "^xgo_[a-f0-9]{40}$"
      },
      "recovery_token": {
        "type": "string",
        "maxLength": 128,
        "minLength": 40
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "idempotentHint": true
  },
  "title": "Recover a paid digital task and receipt"
}

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

Agents: watch_tool({"toolId": "mcp-registry/io.github.moelayyan90/xguard"}) 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%2Fio.github.moelayyan90%2Fxguard.svg)](https://glimind.com/server/mcp-registry%2Fio.github.moelayyan90%2Fxguard?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.moelayyan90%2Fxguard?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.moelayyan90%2Fxguard.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:f2e3205688f04031…, first seen 2026-11-18, included at leaf 327772 of 384,795. Version history · verify what your client received.

Working alternatives

Tools (53)

Compare: most reliable devops servers · most reliable ml servers · most reliable finance servers · most reliable security servers · most reliable knowledge 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 XGuard MCP server down right now?

As of 2026-11-22 17:57 UTC, the XGuard MCP server is degraded with a Glimind reliability score of 59/100 (grade D). Over the last 30 days it answered 73.8% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.

How many tools does XGuard MCP server provide?

XGuard MCP server advertises 53 tools, including compute_health, execute_gpu_job, execute_inference, get_execution_receipt, list_compute_providers.

How do I install XGuard MCP server?

Point your MCP client at this streamable-http endpoint: https://xguardgate.com/mcp

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

Glimind scanned all 53 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 XGuard 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