API Tools
trustdex.app
Provides pricing information, token risk assessment, and API key purchase for a service.
ENDPOINT 1
https://trustdex.app/api/v1/mcp
MCP server metadata
- Name
- trustdex-x402
- Version
- 1.0.0
TrustDex token-safety intelligence, machine-payable per call over the x402 protocol (USDC on Solana/Base/Polygon/Arbitrum/Avalanche; charge-on-success only). Paid tools follow one flow: 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. Docs: https://trustdex.app/docs/api/
Known tools 6
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.trustdex-x402]
url = "https://trustdex.app/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"trustdex-x402": {
"type": "http",
"url": "https://trustdex.app/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: trustdex-x402
Remote MCP URL: https://trustdex.app/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"trustdex-x402": {
"url": "https://trustdex.app/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"trustdex-x402": {
"type": "http",
"url": "https://trustdex.app/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "trustdex-x402",
"transport": "streamable-http",
"url": "https://trustdex.app/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.