AI & Machine Learning
dexl.io
An MCP server for DexL that discovers and prices AI models and tools, supports free-tier chat, and explains x402 payment flow for per-call paid calls.
ENDPOINT 1
https://agents.dexl.io/mcp
MCP server metadata
- Name
- dexl-agents
- Version
- 1.0.0
Free to browse: dexl_catalogue lists every tool, model and product with its price; dexl_price returns the exact cost of a call without running it; dexl_free_chat answers on the free tier. Paid calls need a wallet, which this remote server does not hold - dexl_how_to_pay explains the two ways to make one.
Known tools 5
dexl_catalogueEverything DexL sells with its price: per-call tools, models and packaged products.
Inferred read-onlydexl_modelsChat models callable through the gateway, including the free one (id: dexl-free).
Inferred read-onlydexl_how_to_payHow to pay for a DexL call: the x402 flow, supported chains, and the local client that signs payments for you.
Potential side effectsCONNECT 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.dexl-agents]
url = "https://agents.dexl.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dexl-agents": {
"type": "http",
"url": "https://agents.dexl.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dexl-agents
Remote MCP URL: https://agents.dexl.io/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": {
"dexl-agents": {
"url": "https://agents.dexl.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dexl-agents": {
"type": "http",
"url": "https://agents.dexl.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dexl-agents",
"transport": "streamable-http",
"url": "https://agents.dexl.io/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.