Skip to content

trade-manager MCP server

io.github.amitblecher/trade-manageramitblecherstreamable-httpv1.0.0Scanned

Backtest any trading setup on the S&P 500 vs random days, and see which stocks matched today.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 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

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 trade-manager MCP server can do

The trade-manager MCP server is published by the GitHub account amitblecher. It has 4 tools. It can create or change data (3 tools: test_setup, rule_language and what_happened_today), but cannot delete data. 1 tool only reads.

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 17, 2026, version 1.0.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.

4 tools

Changes things 3Claude Code: ask
  • rule_languageHow to write a rule for test_setup and scan_today: the available names, operators and examples.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    How to write a rule for test_setup and scan_today: the available names, operators and examples.
  • test_setupBacktest a trading setup on every S&P 500 stock since 2017 and compare it with random days.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Backtest a trading setup on every S&P 500 stock since 2017 and compare it with random days. rule: a formula in Trade Manager's language (see the server instructions), e.g. "rsi < 30". horizon_days: how many trading days after the signal to check (1-60, default 20). Returns how often the stock was higher after the signal vs random days on the same stocks (same year, never the signal's own month) and vs the stock's all-days rate, split by period, plus a plain verdict and recent examples. History, not a prediction.
  • what_happened_todayWhat happened on the S&P 500 at the latest close: how many stocks rose and fell, how many sit 10%/20% below their 1-year high, and today's matches for fixed scans (5% drops with RS…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    What happened on the S&P 500 at the latest close: how many stocks rose and fell, how many sit 10%/20% below their 1-year high, and today's matches for fixed scans (5% drops with RSI under 30, breakouts on 2x volume, RSI above 80, 200-day dips in an uptrend, golden crosses, 5% drops), each with its record since 2017 vs random days and, where one exists, a link that opens that exact alert on trademanager.site.
Only reads 1Show 1 read-only tool
  • scan_todayList the S&P 500 stocks that match a setup at the latest daily close (e.g.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the S&P 500 stocks that match a setup at the latest daily close (e.g. "what broke out today on volume"). rule: a formula in Trade Manager's language, e.g. "close > prev_high and volume > volume_avg * 1.5". limit: max stocks to return (default 25). Stocks where the rule just turned true come first, then by volume vs their 20-day average. Uses end-of-day data, not live prices.

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.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 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
3
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp: tools/list returned 4 tools to an anonymous client, including test_setup (write), rule_language (write), what_happened_today (write)

    What this check looks for

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.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trade-manager https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp
claude mcp add --transport http trade-manager https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trade-manager__scan_today"
    ],
    "ask": [
      "mcp__trade-manager__test_setup",
      "mcp__trade-manager__rule_language",
      "mcp__trade-manager__what_happened_today"
    ],
    "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 trade-manager. 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.amitblecher/trade-manager/verify?hash=411af545dd2fe84e53bc024b537e8ace818c4d6bf0a15ef557166b4faedd659a" | jq -e '.changed == false'

Pinned hash 411af545dd2f, from Nov 17, 2026, 06: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.amitblecher/trade-manager/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.amitblecher/trade-manager
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.amitblecher/trade-manager.svg)](https://radar.anlyon.com/servers/io.github.amitblecher/trade-manager)

Source: MCP Registry. Synced Nov 3, 2026, 17:17 UTC.

trade-manager MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the trade-manager MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 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 trade-manager MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the trade-manager 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 trade-manager MCP server have?

4 tools: 3 write, 1 read. test_setup, rule_language, what_happened_today and scan_today.

Does the trade-manager MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the trade-manager MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the trade-manager MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.