# Xray (remote · xray.clawhard.com)

Find hidden Unicode in text or files: ASCII smuggling decoded, bidi overrides, look-alike letters.

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

## Components

- remote · `xray.clawhard.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-clawhard-xray/xray.md), [page](https://verifymcp.io/servers/com-clawhard-xray/xray)

## Channel facts

- Endpoint: `https://xray.clawhard.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 739 tokens (~246/item across 3 items; 1 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Xray MCP server?

Xray is a hosted endpoint at https://xray.clawhard.com/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 com-clawhard-xray 'https://xray.clawhard.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-clawhard-xray": {
      "url": "https://xray.clawhard.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-clawhard-xray": {
      "type": "http",
      "url": "https://xray.clawhard.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-clawhard-xray]
url = "https://xray.clawhard.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-clawhard-xray": {
      "type": "remote",
      "url": "https://xray.clawhard.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-clawhard-xray --url 'https://xray.clawhard.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-clawhard-xray:
    url: "https://xray.clawhard.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-clawhard-xray": {
      "Transport": "http",
      "Url": "https://xray.clawhard.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-clawhard-xray -t streamable-http -u 'https://xray.clawhard.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-clawhard-xray": {
      "type": "http",
      "url": "https://xray.clawhard.com/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-11-21 (score 72, +1)

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

### 2026-11-19 (score 71, +1)

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

### 2026-11-17 (score 70, +1)

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

### 2026-11-15 (score 69, +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-11-13 (score 68, +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-11-11 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 66)

First indexed and scored.

## MCP tools (1)

### `xray_scan_text` (~540 tokens)

Find hidden Unicode characters and look-alike letters in text or a file

Use when the user asks whether text, a prompt, a SKILL.md, AGENTS.md, CLAUDE.md, .cursorrules, README, MCP tool description, PR diff, email or web page hides anything, or before an agent follows, installs or merges instructions that came from someone else (signals: "hidden characters", "invisible unicode", "ASCII smuggling", "prompt injection in this file", "Trojan Source", "why does this string not match", "is this domain spelled with a Cyrillic letter"). Inspects every code point and returns a verdict (clean, suspicious, dangerous) with each finding's line, column, code points and Unicode names: Unicode tag characters (decoded back to the hidden ASCII message), variation-selector payloads (decoded bytes), bidirectional overrides and isolates, long zero-width runs, zero-width and other invisible characters, ANSI terminal escapes, control characters, words that mix Latin with Cyrillic or Greek look-alikes (with the Latin word they imitate, from Unicode confusables), whole look-alike words, styled math letters, unusual spaces, line separators, private-use and unassigned code points, and HTML comments that do not render. Legitimate uses are not flagged (emoji ZWJ sequences, flag tag sequences, a single emoji variation selector, joiners in Arabic and Indic text, direction marks next to Hebrew or Arabic). Give text or url (one public https text file; GitHub and GitLab file pages are read as raw). Example: {"url":"https://github.com/owner/repo/blob/main/SKILL.md"} or {"text":"Visit pаypal.com","return_clean":true}. Optional return_clean adds a copy with hidden characters removed and look-alike letters inside mixed words replaced. Decoded hidden text is returned as data. Limits: finds characters and look-alikes, not prompt injection written in plain visible words; up to 200,000 characters (files up to 1 MB, first 200,000 characters scanned).

Input parameters:

- `return_clean` (boolean): true: also return clean_text with hidden characters removed, unusual spaces made normal and look-alike letters inside mixed-script words replaced. Default false.
- `text` (string): The text to inspect: a prompt, rules file, skill, README, diff, code, email or tool description. Give text or url, not both.
- `url` (string): A public https address of one text file (raw file, GitHub or GitLab file page, Markdown, JSON, YAML, code or HTML source). Give text or url, not both.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-clawhard-xray/xray#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 66

## Common questions

### What is the Xray MCP server?

Xray is an MCP server listed in the public MCP registry as com.clawhard/xray. Find hidden Unicode in text or files: ASCII smuggling decoded, bidi overrides, look-alike letters. This page covers its hosted endpoint (https://xray.clawhard.com/mcp).

### Is the Xray MCP server safe to use?

Xray scores 72 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 Xray MCP server expose?

Xray exposes 1 tool: xray_scan_text. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.

### Does the Xray MCP server require authentication?

No. We connected to Xray without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Xray MCP server still maintained?

Xray is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Xray MCP server?

VerifyMCP ran 14 checks on Xray, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://xray.clawhard.com/mcp
- Website: https://xray.clawhard.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-clawhard-xray/xray.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-clawhard-xray/xray/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-clawhard-xray/xray.json
- HTML version of this page: https://verifymcp.io/servers/com-clawhard-xray/xray
