mcp-registry/io.github.moelayyan90/xguard · registry v6.1.0 · server reports v6.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs 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.
Bounded digital tasks, simple checkout, private result recovery and signed receipts.
Point your MCP client at this streamable-http endpoint: https://xguardgate.com/mcp
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 →
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 →
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 →
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 →
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 →
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
{
"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"
}{
"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"
}{
"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 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.
xguard.preflight ~5,083 tokensxguard.pricing.quote ~5,031 tokensxguard.web.fetch ~3,752 tokensxguard.commerce_compare_offers ~597 tokensxguard.commerce_iam_check ~535 tokensStatic 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.moelayyan90%2Fxguard?ref=badge)
<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>
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.
Compare: most reliable devops servers · most reliable ml servers · most reliable finance servers · most reliable security servers · most reliable knowledge servers
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.
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"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
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.
XGuard MCP server advertises 53 tools, including compute_health, execute_gpu_job, execute_inference, get_execution_receipt, list_compute_providers.
Point your MCP client at this streamable-http endpoint: https://xguardgate.com/mcp
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.
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.