Analytics

preape.ai

Provides pre-trade risk assessment and analysis for tokens on Arc/RadarDEX to help users make informed buying decisions.

1 endpoint2 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://mcp.preape.ai

No auth detected

MCP server metadata

Name: preape
Version: 1.0.0

Capabilities

tools

Server instructions

Use PreApe before buying a RadarDEX token on Arc. Call preape_check first. If CAUTION or you need holders, call preape_analyze ($0.03 USDC on Base via x402). Verdicts: GO, CAUTION, AVOID. Missing data is null.

Known tools 2

preape_check

Quick pre-trade risk check for a token on Arc / RadarDEX before buying.

Potential side effects

preape_analyze

Full pre-trade analysis for an Arc / RadarDEX token before buying.

Potential side effects

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.preape]
url = "https://mcp.preape.ai"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "preape": {
      "type": "http",
      "url": "https://mcp.preape.ai"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: preape
Remote MCP URL: https://mcp.preape.ai

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": {
    "preape": {
      "url": "https://mcp.preape.ai"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "preape": {
      "type": "http",
      "url": "https://mcp.preape.ai"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "preape",
  "transport": "streamable-http",
  "url": "https://mcp.preape.ai"
}

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.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.