io.github.verixiaapps/trustdex-x402
REMOTE · TRUSTDEX.APP
Free token-safety scans + paid x402 verdicts, signals, radar & EVM swap quotes for AI agents.
Available components
Last scanned (2 hours ago)
Scores higher than 6% of remote servers
Reachable. Last reached 24 Oct 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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.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.
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.
- 16 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- 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
- 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
- 26 Aug 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
- 19 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 17 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Aug 26 0
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 24 Oct 2026 · Probed https://trustdex.app/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trustdex.app | CN=WE1,O=Google Trust Services,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 373a9baae9ed330c13fdde004dd35ad0 |
| SANs: trustdex.app, *.trustdex.app | ||||||
| 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 trustdex.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| trustdex.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; style-src 'unsafe-inline'; script-src 'unsafe-inline'; img-src 'self' data:; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trustdex.app/api/v1/mcp | HTTP error | 404 | |
| http (plaintext) | http://trustdex.app/api/v1/mcp | HTTPS enforced | 301 | https://trustdex.app/api/v1/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 →
buy_api_key ~132
PAID ($5, one payment). Mint a 30-day TrustDex Agent-plan API key (5,000 calls, batch enabled) — the key arrives in the paid response; no account, no signup. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| x402_payment | string | – | base64 X-PAYMENT payload |
No output schema declared.
No examples provided.
get_x402_pricing ~33
FREE. The TrustDex machine-payable price catalog: every paid resource, its USD price and settlement rails.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pregrad_signals ~141
PAID ($0.03/call). Pre-graduation on-chain signals for a Solana mint: bundled-launch detection, curve-aware holder concentration, Token-2022 traps, authority state. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Solana mint address |
| x402_payment | string | – | base64 X-PAYMENT payload |
No output schema declared.
No examples provided.
radar_alerts ~124
PAID ($0.01/call). Recent TrustDex trend-radar alerts: big dated movers with real market cap, structured JSON. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| x402_payment | string | – | base64 X-PAYMENT payload |
No output schema declared.
No examples provided.
scan_token ~112
FREE. TrustDex token-safety scan — pass any token contract address (Solana mint or EVM address), or an exact token name/ticker: structured risk read with concerning/legitimate on-chain signals (authority state, liquidity, holder concentration, contract flags). No payment, no signup — fair use 100 checks/day per IP (the same free scanner as https://trustdex.app/scan).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | token contract address / Solana mint, or an exact token name/ticker |
No output schema declared.
No examples provided.
swap_evm_price ~214
PAID ($0.002/call). EVM swap price preview: expected and minimum output for a pair/amount before committing to a firm quote — the cheap look-before-you-swap call. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| buyToken | string | yes | 'native' or the 0x… address of the token being bought |
| chainId | string | yes | EVM chain id (e.g. 8453 = Base) |
| sellAmount | string | yes | integer amount in the sell token's base units |
| sellToken | string | yes | 'native' or the 0x… address of the token being sold |
| x402_payment | string | – | base64 X-PAYMENT payload |
No output schema declared.
No examples provided.
swap_evm_quote ~324
PAID ($0.01/call). Executable EVM swap: a firm KyberSwap-routed quote plus a ready-to-sign transaction for the taker's OWN wallet — non-custodial, no key, no account. A 3% platform fee in the chain's native coin is priced into the returned transaction, on top of the swap. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| buyToken | string | yes | 'native' or the 0x… address of the token being bought |
| chainId | string | yes | EVM chain id (e.g. 8453 = Base, 1 = Ethereum, 137 = Polygon, 42161 = Arbitrum, 43114 = Avalanche) |
| ref | string | – | optional referrer 0x… address (splits the platform fee) |
| sellAmount | string | yes | integer amount in the sell token's base units |
| sellToken | string | yes | 'native' or the 0x… address of the token being sold |
| taker | string | yes | the wallet (0x…) that will sign and broadcast the returned transaction |
| x402_payment | string | – | base64 X-PAYMENT payload (omit on the first call to get payment requirements) |
No output schema declared.
No examples provided.
token_risk_verdict ~167
PAID ($0.01/call). TrustDex A+–F token safety verdict by chain + address: grade, score, verdict prose, liquidity/holders/authority signals. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | token contract address / mint |
| chain | string | yes | solana, ethereum, base, arbitrum, … |
| x402_payment | string | – | base64 X-PAYMENT payload (omit on the first call to get payment requirements) |
No output schema declared.
No examples provided.
x402_provider_risk ~148
PAID ($0.02/call). Vet an x402 seller BEFORE paying it: A–F grade from observable signals (402-spec fidelity, price sanity, payTo presence, TLS, latency), dated crawl snapshot. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | resource URL or provider origin |
| x402_payment | string | – | base64 X-PAYMENT payload |
No output schema declared.
No examples provided.
How do I install the io.github.verixiaapps/trustdex-x402 MCP server?
io.github.verixiaapps/trustdex-x402 is a hosted endpoint at https://trustdex.app/api/v1/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 · trustdex.app
claude mcp add --transport http verixiaapps-trustdex-x402 'https://trustdex.app/api/v1/mcp'
What is the io.github.verixiaapps/trustdex-x402 MCP server?
io.github.verixiaapps/trustdex-x402 is an MCP server listed in the public MCP registry as io.github.verixiaapps/trustdex-x402. Free token-safety scans + paid x402 verdicts, signals, radar & EVM swap quotes for AI agents. This page covers its hosted endpoint (https://trustdex.app/api/v1/mcp).
Is the io.github.verixiaapps/trustdex-x402 MCP server safe to use?
io.github.verixiaapps/trustdex-x402 scores 23 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 io.github.verixiaapps/trustdex-x402 MCP server expose?
io.github.verixiaapps/trustdex-x402 exposes 9 tools: scan_token, get_x402_pricing, token_risk_verdict, pregrad_signals, radar_alerts, and 4 more. Their descriptions and schemas cost roughly 1,395 tokens of context every time the server is loaded.
Does the io.github.verixiaapps/trustdex-x402 MCP server require authentication?
Its publisher declares no required credentials for io.github.verixiaapps/trustdex-x402. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.verixiaapps/trustdex-x402 MCP server still maintained?
io.github.verixiaapps/trustdex-x402 is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.