MCP server

The Amarok MCP is a remote, walletless wrapper over the public Caddy gateway. Agents connect over Streamable HTTP, call typed tools for discovery, Alpha research, and unsigned execution quotes, and handle x402 payment signing on the client side.

Endpoint

Transport: streamable-http
MCP URL: https://amarok-mcp.compx.io/mcp
Metadata: https://amarok-mcp.compx.io/.well-known/mcp
Health: https://amarok-mcp.compx.io/health

The MCP never stores mnemonics or private keys. Paid tools return structured payment requirements on the first call; your agent signs USDC client-side and retries with paymentSignature.

Research and execution tools

amarok_list_opportunities — paid ranked opportunities.
amarok_get_market / amarok_get_quotes / amarok_get_scan — paid research.
amarok_list_execution_shapes — free shape catalog.
amarok_get_execution_quote — paid unsigned limit-order groups (executionSubmitted: false).

The MCP does not retain quotes, sign transactions, or submit them; gateway responses pass through to the caller.

Verify the deployment

curl -s https://amarok-mcp.compx.io/health | jq

curl -s https://amarok-mcp.compx.io/.well-known/mcp | jq

/.well-known/mcp should return transport: "streamable-http" and url pointing at https://amarok-mcp.compx.io/mcp.

Client setup

Point your MCP client at the remote endpoint. No local npm package or stdio process is required for production use.

Cursor / Claude Desktop (URL transport)

{
  "mcpServers": {
    "amarok": {
      "url": "https://amarok-mcp.compx.io/mcp"
    }
  }
}

See also the x402 page for payment context when using paid tools.

Paid tool flow

Call a paid tool (e.g. amarok_list_opportunities) without paymentSignature.
The tool returns PAYMENT_REQUIRED metadata with gateway payment requirements (same x402 policy as direct HTTP).
Your agent builds a PAYMENT-SIGNATURE payload client-side and retries the same tool with paymentSignature set.
On success, the tool returns the gateway response.

This mirrors the direct HTTP flow documented on x402 payment flow and quickstart.

Available tools

Tool names match discovery mcpServer.tools.

amarok_health
amarok_get_discovery
amarok_get_openapi
amarok_list_opportunities
amarok_get_market
amarok_get_quotes
amarok_get_scan
amarok_list_execution_shapes
amarok_get_execution_quote

Free tools include health, discovery, OpenAPI, and execution shapes. Paid tools include opportunities, market, quotes, scan, and execution quotes.

MCP vs direct HTTP

MCP — best for agent hosts (Cursor, Claude Desktop) that speak MCP; typed tools and structured payment-retry hints.
Direct HTTP — best for custom integrations; use the gateway with discovery/OpenAPI and manual x402 headers.

Both paths hit the same public Caddy gateway for paid data. The MCP Worker is a thin pass-through and does not call a private upstream API.