Back to Browse

X402 Example MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).

About

Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).

Remote endpoints: streamable-http: https://mcp.alphabotpro.cloud/v1/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

9 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-imrane2019-alphabotpro": {
      "url": "https://mcp.alphabotpro.cloud/v1/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

AlphaBotPro MCP + x402 Example

A minimal, runnable example showing an AI agent discovering, paying for, and unlocking live trading data over MCP using the x402 machine-payment pattern — no human, no dashboard, no checkout form.

This talks to the real, live AlphaBotPro MCP server. Nothing here is a mock.

What it demonstrates

  1. initialize — standard MCP JSON-RPC handshake
  2. tools/list — discover the available tools
  3. get_catalog — a public tool: prices and sample payloads, no auth
  4. get_signals without a key — a clean, structured payment_required error (the x402 pattern) instead of a silent failure
  5. purchase_access — request a crypto invoice (USDT/USDC on TRON, Polygon or Base) for a paid tier
  6. check_payment — poll until the invoice settles, then receive a scoped API key
  7. get_signals again, now authenticated

Run it

node example.mjs

No dependencies, no API key required to run steps 1–5 (only step 6/7 need a real payment to complete — the script prints the payment instructions and exits there unless you pass --pay, which is left as a manual step since it requires a funded wallet).

Server details

Why this exists

Most "AI-ready" APIs still assume a human signs up, enters a card number, and pastes a key into a config file. That breaks the moment the buyer is an autonomous agent. This server lets an agent discover the price, pay in stablecoins, and start pulling data — all inside one continuous session.

Full write-up: https://alphabotpro.cloud/blog/post/how-ai-agents-pay-for-data-with-crypto-x402-mcp-example

Disclaimer

Trading signals returned by this API are informational tools, not financial advice, and not a guarantee of profit. Trading carries risk of loss. AlphaBotPro is not affiliated with the Model Context Protocol project or the x402 project — this repo is an independent example of using both.

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!