# io.github.xiaoba-dev/atlaxy (remote · api.atlaxy.ai)

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

- Trust score: 60/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.atlaxy.ai`: 60/100 (this document), [markdown](https://verifymcp.io/servers/xiaoba-dev-atlaxy/api.md), [page](https://verifymcp.io/servers/xiaoba-dev-atlaxy/api)

## Channel facts

- Endpoint: `https://api.atlaxy.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 351 tokens (~43/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the io.github.xiaoba-dev/atlaxy MCP server?

io.github.xiaoba-dev/atlaxy is a hosted endpoint at https://api.atlaxy.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xiaoba-dev-atlaxy 'https://api.atlaxy.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xiaoba-dev-atlaxy": {
      "url": "https://api.atlaxy.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xiaoba-dev-atlaxy": {
      "type": "http",
      "url": "https://api.atlaxy.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xiaoba-dev-atlaxy]
url = "https://api.atlaxy.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xiaoba-dev-atlaxy": {
      "type": "remote",
      "url": "https://api.atlaxy.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xiaoba-dev-atlaxy --url 'https://api.atlaxy.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xiaoba-dev-atlaxy:
    url: "https://api.atlaxy.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xiaoba-dev-atlaxy": {
      "Transport": "http",
      "Url": "https://api.atlaxy.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xiaoba-dev-atlaxy -t streamable-http -u 'https://api.atlaxy.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 53, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `search_entities` (~86 tokens)

Search AI products, models, agents and organizations by keyword. Returns ranked matches with scores and why they matched.

Input parameters:

- `continent` (string): L1 continent name, e.g. 'AI Coding'
- `limit` (integer)
- `q` (string, required): Search query
- `score_mode` (string)
- `tag` (string)
- `type` (string)

### `get_entity` (~40 tokens)

Get the full record for one entity by slug: scores (4 explainable dimensions), evidence, sources, tags, links.

Input parameters:

- `slug` (string, required)

### `list_entities` (~53 tokens)

List entities, optionally filtered by continent / type, ranked by score_mode.

Input parameters:

- `continent` (string)
- `entity_type` (string)
- `limit` (integer)
- `score_mode` (string)

### `get_entity_relations` (~53 tokens)

Get an entity's relations (alternatives, built-on, integrations…) with confidence and target names.

Input parameters:

- `limit` (integer)
- `min_confidence` (number)
- `slug` (string, required)

### `compare_entities` (~28 tokens)

Compare 2–5 entities across the four scoring dimensions.

Input parameters:

- `slugs` (array, required)

### `list_tracks` (~24 tokens)

List the 12 AI continents (tracks) with node counts and top nodes.

### `get_taxonomy` (~17 tokens)

Get the full continent + region taxonomy.

### `get_snapshot_meta` (~24 tokens)

Get the current published snapshot metadata: version, counts, freshness, validation.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xiaoba-dev-atlaxy/api#diagnostics

## Score history

- 2026-09-20: 60
- 2026-09-19: 59
- 2026-09-18: 59
- 2026-09-17: 58
- 2026-09-16: 58
- 2026-09-15: 57
- 2026-09-14: 57
- 2026-09-13: 56
- 2026-09-12: 56
- 2026-09-11: 55
- 2026-09-10: 55
- 2026-09-09: 55
- 2026-09-08: 54
- 2026-09-07: 54
- 2026-09-06: 53
- 2026-09-05: 53
- 2026-09-04: 52

## Common questions

### What is the io.github.xiaoba-dev/atlaxy MCP server?

io.github.xiaoba-dev/atlaxy is an MCP server listed in the public MCP registry as io.github.xiaoba-dev/atlaxy. Search 500+ AI products, models, agents and orgs with explainable scores. Read-only MCP for Atlaxy. This page covers its hosted endpoint (https://api.atlaxy.ai/mcp).

### Is the io.github.xiaoba-dev/atlaxy MCP server safe to use?

io.github.xiaoba-dev/atlaxy scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.xiaoba-dev/atlaxy MCP server expose?

io.github.xiaoba-dev/atlaxy exposes 8 tools: search_entities, get_entity, list_entities, get_entity_relations, compare_entities, and 3 more. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.

### Does the io.github.xiaoba-dev/atlaxy MCP server require authentication?

No. We connected to io.github.xiaoba-dev/atlaxy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.xiaoba-dev/atlaxy MCP server still maintained?

io.github.xiaoba-dev/atlaxy is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.atlaxy.ai/mcp
- Repository: https://github.com/xiaoba-dev/ai-world-map
- Changelog RSS feed: https://verifymcp.io/servers/xiaoba-dev-atlaxy/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/xiaoba-dev-atlaxy/api.json
- HTML version of this page: https://verifymcp.io/servers/xiaoba-dev-atlaxy/api