com.xrade/xrade
REMOTE · MCP.XRADE.COM · SCANNED SEP 28
The XRADE record: what you actually own when you buy a tokenised asset. Read-only.
Available components
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 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. 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 Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 336 tokens (~56/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
remote · mcp.xrade.com
claude mcp add --transport http com-xrade-xrade 'https://mcp.xrade.com/mcp'
{
"mcpServers": {
"com-xrade-xrade": {
"url": "https://mcp.xrade.com/mcp"
}
}
} {
"servers": {
"com-xrade-xrade": {
"type": "http",
"url": "https://mcp.xrade.com/mcp"
}
}
} [mcp_servers.com-xrade-xrade] url = "https://mcp.xrade.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-xrade-xrade": {
"type": "remote",
"url": "https://mcp.xrade.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-xrade-xrade --url 'https://mcp.xrade.com/mcp' --transport streamable-http
mcp_servers:
com-xrade-xrade:
url: "https://mcp.xrade.com/mcp" {
"McpServers": {
"com-xrade-xrade": {
"Transport": "http",
"Url": "https://mcp.xrade.com/mcp"
}
}
} assistant mcp add com-xrade-xrade -t streamable-http -u 'https://mcp.xrade.com/mcp'
{
"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.
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.
- 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
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
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 28 Sept 2026 · Probed https://mcp.xrade.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.xrade.com | CN=YE2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 57e095fba061d210d985fa34726651ce94c |
| SANs: mcp.xrade.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.xrade.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| xrade.com. | 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://mcp.xrade.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.xrade.com/mcp | HTTPS enforced | 301 | https://mcp.xrade.com/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 →
coverage ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_stock ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Ticker (e.g. "NVDA") or company name (e.g. "NVIDIA") |
No output schema declared.
No examples provided.
lookup_token ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address (EVM 0x..., Solana mint, Ton or Tron address) |
| chain | string | yes | Chain name, e.g. ethereum, solana, arbitrum, bnb, robinhood, base, plume |
No output schema declared.
No examples provided.
wrapper_record ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| wrapper | string | yes | Wrapper slug or name fragment, e.g. "dinari", "xstocks", "robinhood" |
No output schema declared.
No examples provided.
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.