Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TradeOnyx

REMOTE · TRADEONYX.IO · SCANNED AUG 22

Trading journal with pattern detection: log trades by voice, query your own history.

Available components

remote · tradeonyx.io 38
0 this week 38 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security94
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the TradeOnyx MCP server?

TradeOnyx is a hosted endpoint at https://tradeonyx.io/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 · tradeonyx.io

# add to Claude Code
claude mcp add --transport http io-tradeonyx-tradeonyx 'https://tradeonyx.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-tradeonyx-tradeonyx": {
      "url": "https://tradeonyx.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-tradeonyx-tradeonyx": {
      "type": "http",
      "url": "https://tradeonyx.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-tradeonyx-tradeonyx]
url = "https://tradeonyx.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tradeonyx-tradeonyx": {
      "type": "remote",
      "url": "https://tradeonyx.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-tradeonyx-tradeonyx --url 'https://tradeonyx.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-tradeonyx-tradeonyx:
    url: "https://tradeonyx.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-tradeonyx-tradeonyx": {
      "Transport": "http",
      "Url": "https://tradeonyx.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-tradeonyx-tradeonyx -t streamable-http -u 'https://tradeonyx.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-tradeonyx-tradeonyx": {
      "type": "http",
      "url": "https://tradeonyx.io/mcp"
    }
  }
}

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

Changelog

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.

  • 20 Aug 26 0
    • Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
    • Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
  • 19 Aug 26 +13
    • Transport: fail → unverified ▼ security
    • Authorization: unverified → pass ▲ security
  • 18 Aug 26 −13
    • Transport: unverified → fail ▼ security
    • Authorization: pass → unverified ▼ security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
  • 14 Aug 26 +2
    • Authorization: fail → pass ▲ security
    • First check of Authorization: partial security
  • 13 Aug 26 36

    First indexed and scored.

Diagnostics

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 22 Aug 2026 · Probed https://tradeonyx.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tradeonyx.io CN=YE2,O=Let's Encrypt,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA384 59ab3b2b337e8e3734c8a2a72b93ba3ede4
SANs: *.tradeonyx.io, tradeonyx.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of tradeonyx.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
tradeonyx.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="tradeonyx", resource_metadata="https://tradeonyx.io/.well-known/oauth-protected-resource" 

Bearer realm="tradeonyx", resource_metadata="https://tradeonyx.io/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
www-authenticate Bearer realm="tradeonyx", resource_metadata="https://tradeonyx.io/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://tradeonyx.io/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://tradeonyx.io/mcp
Authorisation server https://app.tradeonyx.io
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tradeonyx.io/mcp Auth required 401
http (plaintext) http://tradeonyx.io/mcp HTTPS enforced 301 https://tradeonyx.io/mcp
MCP tools

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.

No tool schema has been captured from this endpoint yet.

Common questions

What is the TradeOnyx MCP server?

TradeOnyx is an MCP server listed in the public MCP registry as io.tradeonyx/tradeonyx. Trading journal with pattern detection: log trades by voice, query your own history. This page covers its hosted endpoint (https://tradeonyx.io/mcp).

Is the TradeOnyx MCP server safe to use?

TradeOnyx scores 38 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.

Does the TradeOnyx MCP server require authentication?

Yes. TradeOnyx asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the TradeOnyx MCP server still maintained?

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