Autotrade — Autonomous Trading Agents MCP server
com.bitcoinsllm/autotradebitcoinsllm.comstreamable-httpv1.4.2Scanned
Deploy autonomous LLM trading agents and drive them over MCP.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Autotrade — Autonomous Trading Agents MCP server can do
The Autotrade — Autonomous Trading Agents MCP server is published by bitcoinsllm.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: deploy_agent, run_backtest, grant_agent_credentials and agent_execute), but cannot delete data. 2 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.
Last scanned Oct 30, 2026, version 1.4.2.
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.
6 tools
Changes things 4Claude Code: ask
agent_executeRun an ad-hoc command inside the agent's runtime environment (for debugging a strategy or inspecting state).No findings
Why it is in this group
- The name "agent_execute" says "execute": a word for a change.
- The input takes a statement or command to run (input.command), which can change anything it can reach.
Description, as the server wrote it Run an ad-hoc command inside the agent's runtime environment (for debugging a strategy or inspecting state).
deploy_agentCreate and start an autonomous trading agent.No findings
Why it is in this group
- The name "deploy_agent" says "deploy": a word for a change.
Description, as the server wrote it Create and start an autonomous trading agent. Provide a strategy prompt, a model, and the exchange/model keys the agent should use to place orders.
grant_agent_credentialsAttach or rotate the exchange and model-provider keys an agent uses.No findings
Why it is in this group
- The description's first verb is "attach": a word for a change.
Description, as the server wrote it Attach or rotate the exchange and model-provider keys an agent uses. Keys are scoped to that agent.
run_backtestBacktest a strategy against historical market data and return performance stats and an equity curve.No findings
Why it is in this group
- The name "run_backtest" says "run": a word for a change.
Description, as the server wrote it Backtest a strategy against historical market data and return performance stats and an equity curve.
Only reads 2Show 2 read-only tools
agent_logsReturn the recent decision log for an agent — each entry with the model's reasoning and the order placed.No findings
Why it is in this group
- The name "agent_logs" says "log": a word for reading.
Description, as the server wrote it Return the recent decision log for an agent — each entry with the model's reasoning and the order placed.
agent_statusReturn the live status of a deployed agent: PnL, open positions, uptime, error count.No findings
Why it is in this group
- The name "agent_status" says "status": a word for reading.
Description, as the server wrote it Return the live status of a deployed agent: PnL, open positions, uptime, error count.
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, 18:34 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The operation was aborted due to timeout
Posture changes
- Nov 13, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
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.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.4.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http autotrade https://agent.bitcoinsllm.com/mcpclaude mcp add --transport http autotrade https://agent.bitcoinsllm.com/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__autotrade__agent_status",
"mcp__autotrade__agent_logs"
],
"ask": [
"mcp__autotrade__deploy_agent",
"mcp__autotrade__run_backtest",
"mcp__autotrade__grant_agent_credentials",
"mcp__autotrade__agent_execute"
],
"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 autotrade. 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/com.bitcoinsllm/autotrade/verify?hash=8e2bb388cb5d860c09fa110523b8ed953b3a1c8e0c6b6c809ae1a6254ce306d6" | jq -e '.changed == false'Pinned hash 8e2bb388cb5d, from Oct 30, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.bitcoinsllm/autotrade/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.bitcoinsllm/autotrade)Source: MCP Registry. Synced Oct 21, 2026, 17:51 UTC.
Autotrade — Autonomous Trading Agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Autotrade — Autonomous Trading Agents MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 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 Autotrade — Autonomous Trading Agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Autotrade — Autonomous Trading Agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Autotrade — Autonomous Trading Agents MCP server have?
- 6 tools: 4 write, 2 read. deploy_agent, run_backtest, grant_agent_credentials, agent_execute, agent_status and agent_logs.
Does the Autotrade — Autonomous Trading Agents MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Autotrade — Autonomous Trading Agents MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Autotrade — Autonomous Trading Agents MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 30, 2026.