Skip to main content
Glama
README.md
# x402 DEX Market Intelligence API & MCP Server

Real-time DEX token momentum, liquidity health, and whale flow monitoring on Base Mainnet gated with gasless **x402 (EIP-3009)** micropayments.

- **Interactive API Docs:** https://x402-intel-engine-production.up.railway.app/docs
- **OpenAPI Schema:** https://x402-intel-engine-production.up.railway.app/openapi.json
- **Settlement Chain:** Base Mainnet (`8453`)
- **Asset:** USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`)

---

## Available Endpoints & MCP Tools

| Endpoint | Price (USDC) | Description |
| :--- | :--- | :--- |
| `GET /v1/intel/pulse/{token}` | `$0.02` | 5m volume, buy pressure, momentum score |
| `GET /v1/intel/orderbook/{token}` | `$0.05` | DEX liquidity depth & turnover ratio |
| `GET /v1/intel/whale-flow/{token}` | `$0.10` | 1h whale accumulation & distribution signals |

---

## Quickstart: MCP Setup (Claude Desktop / Cursor)

Add the server to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "x402-dex-intel": {
      "command": "python",
      "args": ["/path/to/mcp_server.py"],
      "env": {
        "AGENT_PRIVATE_KEY": "0x_YOUR_FUNDED_BASE_WALLET_PRIVATE_KEY"
      }
    }
  }
}

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct market data aspect: orderbook depth, whale flow, and market pulse. There is no functional overlap, and an agent can easily select the right tool based on the specific intelligence needed.

Naming Consistency5/5

All tool names follow a consistent 'get_' prefix followed by a descriptive noun phrase (orderbook_depth, whale_flow, market_pulse). The naming pattern is uniform and predictable.

Tool Count5/5

With only 3 tools, the server is tightly scoped to its purpose of providing DEX market intelligence. Each tool covers a distinct data category, and the count is well-suited for a focused, specialized server.

Completeness4/5

The tool surface covers the core market intel needs: orderbook, whale activity, and market momentum. Potential minor gaps like historical data or token metadata exist, but for the stated purpose, the coverage is nearly complete without dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues