Is the Xiaoba Dev Atlaxy MCP server down?

mcp-registry/io.github.xiaoba-dev/atlaxy · v2026.09.03

As of 2026-10-19 23:26 UTC, the Xiaoba Dev Atlaxy MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Search 500+ AI products, models, agents and orgs with explainable scores. Read-only MCP for Atlaxy.

claude mcp add --transport http xiaoba-dev-atlaxy-mcp-server https://api.atlaxy.ai/mcp

{
  "mcpServers": {
    "xiaoba-dev-atlaxy-mcp-server": {
      "type": "http",
      "url": "https://api.atlaxy.ai/mcp"
    }
  }
}

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

Agent-readiness: C (71/100)

What to fix (4)

Auto-fix: 8 corrected tool definitions

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

{
  "name": "compare_entities",
  "description": "Compare 2–5 entities across the four scoring dimensions.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slugs"
    ],
    "properties": {
      "slugs": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 5,
        "minItems": 2
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_entity",
  "description": "Get the full record for one entity by slug: scores (4 explainable dimensions), evidence, sources, tags, links.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_entity_relations",
  "description": "Get an entity's relations (alternatives, built-on, integrations…) with confidence and target names.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      },
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1
      },
      "min_confidence": {
        "type": "number",
        "default": 0.7,
        "maximum": 1,
        "minimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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.xiaoba-dev/atlaxy"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.xiaoba-dev/atlaxy"}) 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 (~663 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• search_entities ~172 tokens
• list_entities ~121 tokens
• get_entity_relations ~105 tokens
• compare_entities ~69 tokens
• get_entity ~67 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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xiaoba-dev%2Fatlaxy.svg)](https://glimind.com/server/mcp-registry%2Fio.github.xiaoba-dev%2Fatlaxy?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.xiaoba-dev%2Fatlaxy?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xiaoba-dev%2Fatlaxy.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xiaoba-dev%2Fatlaxy.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.xiaoba-dev%2Fatlaxy?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:549f304a18d2665d…, first seen 2026-10-17, included at leaf 2104 of 29,433. Version history · verify what your client received.

Tools (8)

• compare_entities
• get_entity
• get_entity_relations
• get_snapshot_meta
• get_taxonomy
• list_entities
• list_tracks
• search_entities

Compare: most reliable data servers · most reliable knowledge servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Xiaoba Dev Atlaxy MCP server down right now?

As of 2026-10-19 23:26 UTC, the Xiaoba Dev Atlaxy MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Xiaoba Dev Atlaxy MCP server provide?

Xiaoba Dev Atlaxy MCP server advertises 8 tools, including compare_entities, get_entity, get_entity_relations, get_snapshot_meta, get_taxonomy.

How do I install Xiaoba Dev Atlaxy MCP server?

Point your MCP client at this streamable-http endpoint: https://api.atlaxy.ai/mcp

Is the Xiaoba Dev Atlaxy MCP server safe to connect to an AI agent?

Glimind scanned all 8 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 Xiaoba Dev Atlaxy 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.