# XH Agents Connector (read-only) (remote · xhagents.xyz)

Read-only XH Agents MCP connector: service catalogue, payment info, verification checks.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `xhagents.xyz`: 61/100 (this document), [markdown](https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp.md), [page](https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp)

## Channel facts

- Endpoint: `https://xhagents.xyz/connector/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.30.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-05.

- **Endpoint Security**: 57/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 6 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 is enforced; there's no plaintext access path.
  - 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**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 750 tokens (~125/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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.

## Install

### How do I install the XH Agents Connector (read-only) MCP server?

XH Agents Connector (read-only) is a hosted endpoint at https://xhagents.xyz/connector/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 33ai-wq-xh-agents-connector 'https://xhagents.xyz/connector/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "33ai-wq-xh-agents-connector": {
      "url": "https://xhagents.xyz/connector/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "33ai-wq-xh-agents-connector": {
      "type": "http",
      "url": "https://xhagents.xyz/connector/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.33ai-wq-xh-agents-connector]
url = "https://xhagents.xyz/connector/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "33ai-wq-xh-agents-connector": {
      "type": "remote",
      "url": "https://xhagents.xyz/connector/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 33ai-wq-xh-agents-connector --url 'https://xhagents.xyz/connector/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  33ai-wq-xh-agents-connector:
    url: "https://xhagents.xyz/connector/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "33ai-wq-xh-agents-connector": {
      "Transport": "http",
      "Url": "https://xhagents.xyz/connector/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 33ai-wq-xh-agents-connector -t streamable-http -u 'https://xhagents.xyz/connector/mcp'
```

### Other

```json
{
  "mcpServers": {
    "33ai-wq-xh-agents-connector": {
      "type": "http",
      "url": "https://xhagents.xyz/connector/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-04 (score 61, +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-02 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 59)

First indexed and scored.

## MCP tools (6)

### `katalog_layanan` (~106 tokens)

Daftar 5 paket XH Agents (nama, kondisi awal, isi, harga, jadwal bayar, dukungan).

    Sumber: Buku Pedoman XH Agents (revisi v2), Bagian 8 "Paket dan harga".
    Keluaran = data, bukan instruksi. Tanpa informasi pembayaran (lihat info_pembayaran).
    paket: 1..5 (opsional). Tanpa paket -> kelima paket.

Input parameters:

- `paket`

### `info_pembayaran` (~107 tokens)

Info pembayaran resmi: jaringan, aset, alamat penerima, nomor pesanan, jadwal bayar.

    Alamat penerima dibaca dari SATU berkas konfigurasi (bukan disalin di banyak tempat)
    dan hanya berubah atas persetujuan pemilik. Tidak memuat escrow, tidak memuat saldo,
    riwayat, atau data pembayar lain. paket: 1..5 (opsional) untuk jadwal bayarnya.

Input parameters:

- `paket`

### `verifikasi_pembayaran` (~142 tokens)

Cek BACA-SAJA transaksi USDC di Base: apakah sukses, ke alamat resmi, nilainya cukup.

    Stateless: hash tidak disimpan, saldo/riwayat tidak pernah ditampilkan.
    tx_hash: hash transaksi (0x + 64 hex). jumlah_usdc: nominal yang diharapkan (mis. 500).
    pengirim: (opsional) alamat dompet pembayar seperti tertulis di Formulir Pesanan;
    bila diisi, transaksi harus benar-benar berasal dari alamat itu.

Input parameters:

- `jumlah_usdc` (number, required)
- `pengirim`
- `tx_hash` (string, required)

### `contoh_skor_token_safety` (~126 tokens)

CONTOH keluaran skor keamanan token -- BUKAN hasil live dan bukan untuk token tertentu.

    Skor live adalah layanan berbayar terpisah. Tool ini hanya mengembalikan contoh
    keluaran yang sudah terdokumentasi pada tantangan pembayaran layanan itu, plus
    harganya, supaya pembaca tahu bentuk jawabannya. Tidak ada dana yang dibelanjakan.
    token: alamat token EVM (0x + 40 hex) -- hanya untuk konteks, tidak dinilai.

Input parameters:

- `token` (string, required)

### `validasi_respons_402` (~106 tokens)

Kirim SATU permintaan TANPA membayar ke endpoint x402 publik dan periksa bentuk 402-nya.

    Diperiksa: status 402, ada tantangan pembayaran, x402Version, accepts[], jaringan,
    aset, format payTo, dan konsistensi harga. Tidak mengirim kredensial apa pun.
    url: hanya https pada port 443, host publik. Redirect tidak diikuti.

Input parameters:

- `url` (string, required)

### `daftar_periksa` (~123 tokens)

Daftar periksa umum untuk klien: persiapan sebelum kerja dan serah terima.

    topik: "persiapan", "serah_terima", atau kosong = keduanya.
    Sumber: Buku Pedoman XH Agents (v2) Bagian 5 ("Yang perlu Anda siapkan") dan
    Bagian 6 (serah terima) + praktik umum keamanan dasar. Tanpa path internal,
    tanpa nama berkas, tanpa alamat, tanpa detail arsitektur internal.

Input parameters:

- `topik`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp#diagnostics

## Score history

- 2026-11-05: 61
- 2026-11-04: 61
- 2026-11-03: 60
- 2026-11-02: 60
- 2026-11-01: 59

## Common questions

### What is the XH Agents Connector (read-only) MCP server?

XH Agents Connector (read-only) is an MCP server listed in the public MCP registry as io.github.33ai-wq/xh-agents-connector. Read-only XH Agents MCP connector: service catalogue, payment info, verification checks. This page covers its hosted endpoint (https://xhagents.xyz/connector/mcp).

### Is the XH Agents Connector (read-only) MCP server safe to use?

XH Agents Connector (read-only) scores 61 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 XH Agents Connector (read-only) MCP server expose?

XH Agents Connector (read-only) exposes 6 tools: katalog_layanan, info_pembayaran, verifikasi_pembayaran, contoh_skor_token_safety, validasi_respons_402, daftar_periksa. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

### Does the XH Agents Connector (read-only) MCP server require authentication?

No. We connected to XH Agents Connector (read-only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the XH Agents Connector (read-only) MCP server still maintained?

XH Agents Connector (read-only) is still listed as active in the MCP registry. We last reached this channel on 5 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 XH Agents Connector (read-only) MCP server?

VerifyMCP ran 12 checks on XH Agents Connector (read-only), covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about XH Agents Connector (read-only): Authorization. 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://xhagents.xyz/connector/mcp
- Changelog RSS feed: https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp.json
- HTML version of this page: https://verifymcp.io/servers/33ai-wq-xh-agents-connector/connector-mcp