Is the X Ego MCP server down?

mcp-registry/com.x-ego/x-ego · v1.0.0

degraded
Last checked 2026-10-24 17:53 UTC · handshake 684ms

As of 2026-10-24 17:53 UTC, the X Ego MCP server is degraded with a Glimind reliability score of 55/100 (grade D). Over the last 30 days it answered 89.9% of Glimind's liveness checks. It had 586 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
89.9%
checks observed
4,912
outages (90d)
586
tools
4

Human approval for irreversible AI agent actions, bound to the exact tool call by a passkey tap

Install X Ego MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http x-ego-mcp-server https://mcp.x-ego.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "x-ego-mcp-server": {
      "type": "http",
      "url": "https://mcp.x-ego.com/mcp"
    }
  }
}

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

Agent-readiness: B (83/100)

B (83/100): 1 error(s), 2 warning(s) across 4 tool(s); ~2,951 tokens of tool definitions.
Scores higher than 40% of 15,639 MCP servers Glimind has audited.
Its tool list costs an agent ~2,951 tokens per session — more than 50% of servers.
82 → 83 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost78
Client compatibility70
Protocol100
Reliability5
Stability100

What to fix (4)

Reachable 89.9% of the time over the last 30 days; median recovery 8 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.

1 tool definition(s) exceed ~1,200 tokens each (largest: xego_request_proof_url, ~1,363).

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 ~763 tokens every session. How to fix →

Tools: xego_request_proof_url · saves ~763 tokens/session

Handshake + tools/list takes ~2,389 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.

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 →

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

Agents: watch_tool({"toolId": "mcp-registry/com.x-ego/x-ego"}) 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%2Fcom.x-ego%2Fx-ego.svg)](https://glimind.com/server/mcp-registry%2Fcom.x-ego%2Fx-ego?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.x-ego%2Fx-ego?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.x-ego%2Fx-ego.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.x-ego%2Fx-ego.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.x-ego%2Fx-ego?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:33422c4543b2ee90…, first seen 2026-10-17, included at leaf 1825 of 60,273. Version history · verify what your client received.

Working alternatives

Tools (4)

Compare: most reliable security servers · most reliable other 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 X Ego MCP server down right now?

As of 2026-10-24 17:53 UTC, the X Ego MCP server is degraded with a Glimind reliability score of 55/100 (grade D). Over the last 30 days it answered 89.9% of Glimind's liveness checks. It had 586 outages in 90 days, with a median recovery of 8 minutes.

How many tools does X Ego MCP server provide?

X Ego MCP server advertises 4 tools, including xego_check_pairwise_seen_before, xego_request_proof_url, xego_verify_action, xego_verify_proof.

How do I install X Ego MCP server?

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

Is the X Ego MCP server safe to connect to an AI agent?

Glimind scanned all 4 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 X Ego 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