# com.xrade/xrade (remote · mcp.xrade.com)

The XRADE record: what you actually own when you buy a tokenised asset. Read-only.

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

## Components

- remote · `mcp.xrade.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-xrade-xrade/mcp.md), [page](https://verifymcp.io/servers/com-xrade-xrade/mcp)

## Channel facts

- Endpoint: `https://mcp.xrade.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.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-28.

- **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 4 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**: 45/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 336 tokens (~56/item across 6 items; 4 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 com.xrade/xrade MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-xrade-xrade": {
      "type": "http",
      "url": "https://mcp.xrade.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-09-28 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, +1)

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

### 2026-09-25 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 66, +1)

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

### 2026-09-20 (score 65, +1)

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

### 2026-09-18 (score 64, +1)

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

### 2026-09-16 (score 63, +1)

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

### 2026-09-14 (score 62, +1)

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

## MCP tools (4)

### `lookup_token` (~118 tokens)

The pre-trade check. Look up a token by chain and contract address: which legal wrapper issued it, what holding it entitles you to, with the supporting quotes. A token XRADE has not covered gets an explicit 'not covered' answer, never a blank.

Input parameters:

- `address` (string, required): Token contract address (EVM 0x..., Solana mint, Ton or Tron address)
- `chain` (string, required): Chain name, e.g. ethereum, solana, arbitrum, bnb, robinhood, base, plume

### `lookup_stock` (~81 tokens)

Look up a stock or asset by ticker or name. Returns every tokenised version the record holds, grouped by legal wrapper, plus tokens seen on chain that are not yet resolved. Versions are unranked and listed alphabetically.

Input parameters:

- `query` (string, required): Ticker (e.g. "NVDA") or company name (e.g. "NVIDIA")

### `wrapper_record` (~90 tokens)

The full legal record of one wrapper: structure, holder claim, insolvency ranking, redemption, dividends, voting, transfer restrictions. Every stated fact carries its supporting quote, source and dates. Fields nobody examined and fields no document discloses are distinguished and say so.

Input parameters:

- `wrapper` (string, required): Wrapper slug or name fragment, e.g. "dinari", "xstocks", "robinhood"

### `coverage` (~39 tokens)

What the record covers and, as importantly, what it knows it has not covered: the denominator of tokens seen on chain and not yet resolved to any wrapper.

## Diagnostics

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

## Score history

- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 66
- 2026-09-23: 66
- 2026-09-22: 65
- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62
- 2026-09-14: 62
- 2026-09-13: 61
- 2026-09-12: 61
- 2026-09-11: 60
- 2026-09-10: 60
- 2026-09-09: 59
- 2026-09-08: 59

## Common questions

### What is the com.xrade/xrade MCP server?

com.xrade/xrade is an MCP server listed in the public MCP registry as com.xrade/xrade. The XRADE record: what you actually own when you buy a tokenised asset. Read-only. This page covers its hosted endpoint (https://mcp.xrade.com/mcp).

### Is the com.xrade/xrade MCP server safe to use?

com.xrade/xrade scores 68 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 com.xrade/xrade MCP server expose?

com.xrade/xrade exposes 4 tools: lookup_token, lookup_stock, wrapper_record, coverage. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.

### Does the com.xrade/xrade MCP server require authentication?

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

### Is the com.xrade/xrade MCP server still maintained?

com.xrade/xrade is still listed as active in the MCP registry. We last reached this channel on 28 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://mcp.xrade.com/mcp
- Website: https://www.xrade.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-xrade-xrade/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-xrade-xrade/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-xrade-xrade/mcp