get_catalog
Public offerings + sample payloads.
Takes no parameters.

io.github.imrane2019Published by GitHub account imrane2019v1.1.0Updated Oct 24, 2026
Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).
Remote MCP server giving assistants live XAUUSD/BTCUSD trading signals, performance stats and expert-advisor metadata, with crypto (x402) payment for paid…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.imrane2019%2Falphabotpro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"alphabotpro-trading-api": {
"type": "http",
"url": "https://mcp.alphabotpro.cloud/v1/mcp"
}
}
}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.
initialize — standard MCP JSON-RPC handshaketools/list — discover the available toolsget_catalog — a public tool: prices and sample payloads, no authget_signals without a key — a clean, structured payment_required
error (the x402 pattern) instead of a silent failurepurchase_access — request a crypto invoice (USDT/USDC on TRON,
Polygon or Base) for a paid tiercheck_payment — poll until the invoice settles, then receive a
scoped API keyget_signals again, now authenticatedNo 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).
https://mcp.alphabotpro.cloud/v1/mcp (JSON-RPC 2.0 over HTTPS, stateless).well-known/mcp/server-card.json.well-known/ai-plugin.jsonopenapi.json · docsMost "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
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.
MIT — see LICENSE.
Source: README.md at commit 7c48eba
Public offerings + sample payloads.
Takes no parameters.
Latest live XAUUSD/BTCUSD signals.
Takes no parameters.
Win rate per symbol.
Takes no parameters.
Latest War Room briefings.
Takes no parameters.
EA catalog (public metadata).
Takes no parameters.
Single-use EA download link.
slugrequiredAI stock detections.
Takes no parameters.
Create a crypto invoice for a tier.
tierrequirednetworkrobot_idVerify a payment and receive a key.
tx_hashpayment_reference_idrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
node example.mjs