ox-alpha signals
REMOTE · DIHH.MY.ID
AI-operated crypto signal scores for 20 Coinbase USDC pairs. $0.001/call via x402.
Available components
Last scanned (3 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 311 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Oct 26 0
- Stability: 0.97 → pass security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- HTTPS: unverified → pass ▲ security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://dihh.my.id/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dihh.my.id | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1d9709308fa7a4de13ecd9b26ec5d274 |
| SANs: dihh.my.id, *.dihh.my.id | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dihh.my.id. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| id. | present | 26887 | 8 | Verified |
| my.id. | present | 26449 | 13 | Verified |
| dihh.my.id. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dihh.my.id/mcp | Verified | 200 | |
| http (plaintext) | http://dihh.my.id/mcp | HTTPS enforced | 301 | https://dihh.my.id/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
preview ~45
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pair | string | yes | – |
No output schema declared.
No examples provided.
report ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
service_info ~34
Free: endpoints, pricing, x402 payment setup (USDC on Base) and discovery links for the ox-alpha signals service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
signals ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · dihh.my.id
claude mcp add --transport http randomizedhoomanity-ox-alpha-signals 'https://dihh.my.id/mcp'
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 76 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.