AlphaBotPro Trading API MCP server
io.github.imrane2019/alphabotproimrane2019streamable-httpv1.1.0Scanned
Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).
9 tools: 2 do something that can't be undone and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AlphaBotPro Trading API MCP server can do
The AlphaBotPro Trading API MCP server is published by the GitHub account imrane2019. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (purchase_access and check_payment), but cannot delete data. 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Can't be undone 2Claude Code: ask
check_paymentVerify a payment and receive a key.No findings
Why it is in this group
- The name "check_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Verify a payment and receive a key.
purchase_accessCreate a crypto invoice for a tier.No findings
Why it is in this group
- The name "purchase_access" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Create a crypto invoice for a tier.
Only reads 7Show 7 read-only tools
get_catalogPublic offerings + sample payloads.No findings
Why it is in this group
- The name "get_catalog" says "get": a word for reading.
Description, as the server wrote it Public offerings + sample payloads.
get_ea_downloadSingle-use EA download link.No findings
Why it is in this group
- The name "get_ea_download" says "get": a word for reading.
Description, as the server wrote it Single-use EA download link.
get_signal_performanceWin rate per symbol.No findings
Why it is in this group
- The name "get_signal_performance" says "get": a word for reading.
Description, as the server wrote it Win rate per symbol.
get_signalsLatest live XAUUSD/BTCUSD signals.No findings
Why it is in this group
- The name "get_signals" says "get": a word for reading.
Description, as the server wrote it Latest live XAUUSD/BTCUSD signals.
get_stock_catalogAI stock detections.No findings
Why it is in this group
- The name "get_stock_catalog" says "get": a word for reading.
Description, as the server wrote it AI stock detections.
get_warroom_analysisLatest War Room briefings.No findings
Why it is in this group
- The name "get_warroom_analysis" says "get": a word for reading.
Description, as the server wrote it Latest War Room briefings.
list_expert_advisorsEA catalog (public metadata).No findings
Why it is in this group
- The name "list_expert_advisors" says "list": a word for reading.
Description, as the server wrote it EA catalog (public metadata).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.alphabotpro.cloud/v1/mcp: tools/list returned 9 tools to an anonymous client, including purchase_access (irreversible), check_payment (irreversible)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http alphabotpro https://mcp.alphabotpro.cloud/v1/mcpclaude mcp add --transport http alphabotpro https://mcp.alphabotpro.cloud/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__alphabotpro__get_catalog",
"mcp__alphabotpro__get_signals",
"mcp__alphabotpro__get_signal_performance",
"mcp__alphabotpro__get_warroom_analysis",
"mcp__alphabotpro__list_expert_advisors",
"mcp__alphabotpro__get_ea_download",
"mcp__alphabotpro__get_stock_catalog"
],
"ask": [
"mcp__alphabotpro__purchase_access",
"mcp__alphabotpro__check_payment"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as alphabotpro. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.imrane2019/alphabotpro/verify?hash=5d61023bc18ca967dc3325cff560d5d6c4253b0c15491598f50c373839def0fa" | jq -e '.changed == false'Pinned hash 5d61023bc18c, from Nov 19, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.imrane2019/alphabotpro/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.imrane2019/alphabotpro)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:36 UTC.
AlphaBotPro Trading API MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AlphaBotPro Trading API MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AlphaBotPro Trading API MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AlphaBotPro Trading API MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: purchase_access and check_payment.
What tools does the AlphaBotPro Trading API MCP server have?
- 9 tools: 2 irreversible, 7 read. purchase_access, check_payment, get_catalog, get_signals, get_signal_performance, get_warroom_analysis, list_expert_advisors, get_ea_download and 1 more.
Does the AlphaBotPro Trading API MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AlphaBotPro Trading API MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AlphaBotPro Trading API MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.