mcpField
A
AlphaBotPro Trading API

AlphaBotPro Trading API

Remote
alphabotpro.cloudFinance0Updated 7w ago
RepositoryVisit website

About AlphaBotPro Trading API

AlphaBotPro Trading API is an MCP server for AI agents that need live XAUUSD and BTCUSD trading signals. It combines public catalog discovery with x402 stablecoin payment and scoped API access.

Key features

  1. 01Public price and sample catalog
  2. 02Live XAUUSD and BTCUSD signals
  3. 03Crypto invoice purchase flow
  4. 04Payment polling and scoped API key

Use cases

  1. 01Review signal prices before purchase
  2. 02Pay for signal access with stablecoins
  3. 03Fetch signals after payment verification

MCP support

Exposes an MCP endpoint with tools for catalog discovery, signal retrieval, access purchase, and payment checks. The payment flow uses x402 and returns a scoped API key after settlement.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.alphabotpro.cloud/v1/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

9

This tool takes no parameters.

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.