NexoTrade
REMOTE · API.NEXOTRADE.COM
Crypto data: Bitcoin zone, fear & greed, funding, calendar, liquidation map and your TradeAudit.
Available components
Last scanned (9 hours ago)
Scores higher than 28% 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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
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
Tool Safety0
- Tool safety 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: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
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 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- 29 Oct 26 38
First indexed and scored.
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://api.nexotrade.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nexotrade.com | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e0ffe03255118d841314bffc7d1fefbb |
| SANs: nexotrade.com, api.nexotrade.com, *.api.nexotrade.com | ||||||
| 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 api.nexotrade.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nexotrade.com. | 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 resource_metadata="https://api.nexotrade.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.nexotrade.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
| www-authenticate | Bearer resource_metadata="https://api.nexotrade.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.nexotrade.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.nexotrade.com/mcp |
| Authorisation server | https://api.nexotrade.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.nexotrade.com/mcp | Auth required | 401 | |
| http (plaintext) | http://api.nexotrade.com/mcp | HTTPS enforced | 301 | https://api.nexotrade.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 →
bitcoin_zone Bitcoin zone ~77
Bitcoin zone: a score from 1 to 100 of how high or low Bitcoin is compared with its own last 4 years (trend, momentum, funding, fear and greed), with its parts. Not cheap/expensive and not a signal.
| Name | Type | Req | Description |
|---|---|---|---|
| historico | string | – | With 1, also the score for each day. |
No output schema declared.
No examples provided.
economic_calendar Economic calendar ~95
This week's or next week's economic releases: time, importance, forecast, previous and actual value.
| Name | Type | Req | Description |
|---|---|---|---|
| idioma | string | – | The language of the data names (without it, Spanish). |
| importancia | string | – | Only these importance levels, separated by commas. Without it, only high importance. |
| paises | string | – | Only these countries, separated by commas. |
| semana | string | – | This week or the next one. |
No output schema declared.
No examples provided.
fear_greed Fear and greed index ~54
Today's crypto fear and greed index (0-100), its band, and its value yesterday and 7 and 30 days ago.
| Name | Type | Req | Description |
|---|---|---|---|
| historico | string | – | With 1, also the last 30 days. |
No output schema declared.
No examples provided.
funding Funding rates ~46
Average 8-hour funding rate of perpetual futures, in %, per coin, across exchanges.
| Name | Type | Req | Description |
|---|---|---|---|
| moneda | string | – | The coin for the last 30 days series (without it, BTC). |
No output schema declared.
No examples provided.
liquidation_map Liquidation map ~154
Liquidation map zones for Bitcoin or Ethereum: where liquidations cluster, on which side and how strong. No prices or amounts.
| Name | Type | Req | Description |
|---|---|---|---|
| antiguedad | string | – | Only the money that came in during that time. |
| apalancamiento | string | – | Only those leverage levels, separated by commas (3,5,10). |
| en | string | – | A past moment, in ISO 8601 with its time zone (up to 30 days back). |
| horizonte | string | – | The map horizon (without it, 1h). |
| minima | string | – | The minimum strength of the zones. |
| moneda | string | yes | In the path: bitcoin or ethereum (ethereum, with the full map). |
No output schema declared.
No examples provided.
my_alerts My alerts ~52
The key owner's own alerts: type, parameters, whether each is active or paused, and when it last fired. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| idioma | string | – | The language of the texts (without it, Spanish). |
No output schema declared.
No examples provided.
my_rank My rank ~52
The key owner's own rank: their current rank, their 30-day traded volume, what the next rank needs and their rank history.
| Name | Type | Req | Description |
|---|---|---|---|
| idioma | string | – | The language of the texts (without it, Spanish). |
No output schema declared.
No examples provided.
tradeaudit_summary TradeAudit summary ~157
Summary of the key owner's own closed trades in TradeAudit for a period: net result, win rate, by pair, side, month, weekday and hour, leverage, streaks, and plain-language conclusions. Amounts are in USDT.
| Name | Type | Req | Description |
|---|---|---|---|
| conexion | string | – | Only those of this connected account (its id, from “conexiones”). |
| lado | string | – | Only longs or only shorts. |
| par | string | – | Only those of this pair, like BTC/USDT. |
| periodo | string | – | The period (without it, the last 30 days). |
| zona | string | – | Your time zone (IANA, like Europe/Madrid), for days and months (without it, UTC). |
No output schema declared.
No examples provided.
tradeaudit_trades TradeAudit trades ~140
The key owner's own closed trades in TradeAudit, newest first, 50 per page. Pass `antes` with the previous page's `siguiente` for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| antes | string | – | For the next page: the value of “siguiente” from the previous response. |
| conexion | string | – | Only those of this connected account (its id, from “conexiones”). |
| lado | string | – | Only longs or only shorts. |
| par | string | – | Only those of this pair, like BTC/USDT. |
| periodo | string | – | The period (without it, the last 30 days). |
No output schema declared.
No examples provided.
How do I install the NexoTrade MCP server?
NexoTrade is a hosted endpoint at https://api.nexotrade.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 · api.nexotrade.com
claude mcp add --transport http com-nexotrade-api 'https://api.nexotrade.com/mcp'
What is the NexoTrade MCP server?
NexoTrade is an MCP server listed in the public MCP registry as com.nexotrade/api. Crypto data: Bitcoin zone, fear & greed, funding, calendar, liquidation map and your TradeAudit. This page covers its hosted endpoint (https://api.nexotrade.com/mcp).
Is the NexoTrade MCP server safe to use?
NexoTrade 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.
What tools does the NexoTrade MCP server expose?
NexoTrade exposes 9 tools: bitcoin_zone, fear_greed, funding, economic_calendar, liquidation_map, and 4 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.
Does the NexoTrade MCP server require authentication?
Yes. NexoTrade 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 NexoTrade MCP server still maintained?
NexoTrade 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.