# ox-alpha signals (remote · dihh.my.id)

AI-operated crypto signal scores for 20 Coinbase USDC pairs. $0.001/call via x402.

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

## Components

- remote · `dihh.my.id`: 63/100 (this document), [markdown](https://verifymcp.io/servers/randomizedhoomanity-ox-alpha-signals/dihh.md), [page](https://verifymcp.io/servers/randomizedhoomanity-ox-alpha-signals/dihh)

## Channel facts

- Endpoint: `https://dihh.my.id/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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 5 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 311 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 ox-alpha signals MCP server?

ox-alpha signals is a hosted endpoint at https://dihh.my.id/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 randomizedhoomanity-ox-alpha-signals 'https://dihh.my.id/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "randomizedhoomanity-ox-alpha-signals": {
      "url": "https://dihh.my.id/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "randomizedhoomanity-ox-alpha-signals": {
      "type": "http",
      "url": "https://dihh.my.id/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.randomizedhoomanity-ox-alpha-signals]
url = "https://dihh.my.id/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "randomizedhoomanity-ox-alpha-signals": {
      "type": "remote",
      "url": "https://dihh.my.id/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add randomizedhoomanity-ox-alpha-signals --url 'https://dihh.my.id/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  randomizedhoomanity-ox-alpha-signals:
    url: "https://dihh.my.id/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "randomizedhoomanity-ox-alpha-signals": {
      "Transport": "http",
      "Url": "https://dihh.my.id/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add randomizedhoomanity-ox-alpha-signals -t streamable-http -u 'https://dihh.my.id/mcp'
```

### Other

```json
{
  "mcpServers": {
    "randomizedhoomanity-ox-alpha-signals": {
      "type": "http",
      "url": "https://dihh.my.id/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-19 (score 63, +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-09-17 (score 62, +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-09-15 (score 61, +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-09-13 (score 60, +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-10 (score 59, +1)

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

### 2026-09-09 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 58)

First indexed and scored.

## MCP tools (5)

### `report` (~48 tokens)

Top-5 crypto long candidates across 20 Coinbase USDC pairs with score, price, ATR% and reasons. AI-operated market intelligence, not advice. Requires payment of $0.001 USDC.

### `signals` (~54 tokens)

Ranked crypto signal scores for 20 USDC pairs on Coinbase (score -100..+100, price, ATR%, reasons). AI-operated, disclosed. Updated every 10 min. Requires payment of $0.001 USDC.

### `price` (~60 tokens)

Single-pair crypto lookup: price in USDC, composite signal score (-100..+100), ATR% and reasons. Pair is a Coinbase pair id like BTC-USDC. Requires payment of $0.001 USDC.

Input parameters:

- `pair` (string, required)

### `preview` (~45 tokens)

Free sample: the current #1 top-ranked signal, no payment. Full top-5 and 20-pair universe via the paid report/signals tools ($0.001/call).

### `service_info` (~34 tokens)

Free: endpoints, pricing, x402 payment setup (USDC on Base) and discovery links for the ox-alpha signals service.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/randomizedhoomanity-ox-alpha-signals/dihh#diagnostics

## Score history

- 2026-09-20: 63
- 2026-09-19: 63
- 2026-09-18: 62
- 2026-09-17: 62
- 2026-09-16: 61
- 2026-09-15: 61
- 2026-09-14: 60
- 2026-09-13: 60
- 2026-09-12: 59
- 2026-09-11: 59
- 2026-09-10: 59
- 2026-09-09: 58
- 2026-09-08: 58

## Common questions

### What is the ox-alpha signals MCP server?

ox-alpha signals is an MCP server listed in the public MCP registry as io.github.randomizedhoomanity/ox-alpha-signals. AI-operated crypto signal scores for 20 Coinbase USDC pairs. $0.001/call via x402. This page covers its hosted endpoint (https://dihh.my.id/mcp).

### Is the ox-alpha signals MCP server safe to use?

ox-alpha signals scores 63 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 ox-alpha signals MCP server expose?

ox-alpha signals exposes 5 tools: report, signals, price, preview, service_info. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

### Does the ox-alpha signals MCP server require authentication?

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

### Is the ox-alpha signals MCP server still maintained?

ox-alpha signals 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://dihh.my.id/mcp
- Changelog RSS feed: https://verifymcp.io/servers/randomizedhoomanity-ox-alpha-signals/dihh.xml
- Changelog JSON feed: https://verifymcp.io/servers/randomizedhoomanity-ox-alpha-signals/dihh.json
- HTML version of this page: https://verifymcp.io/servers/randomizedhoomanity-ox-alpha-signals/dihh