# io.github.amitblecher/trade-manager (remote · amitblecher10--trade-manager-mcp-web.us-east.modal.run)

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

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `amitblecher10--trade-manager-mcp-web.us-east.modal.run`: 67/100 (this document), [markdown](https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web.md), [page](https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web)

## Channel facts

- Endpoint: `https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 963 tokens (~240/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (25% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.amitblecher/trade-manager MCP server?

io.github.amitblecher/trade-manager is a hosted endpoint at https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "amitblecher-trade-manager": {
      "url": "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "amitblecher-trade-manager": {
      "type": "http",
      "url": "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.amitblecher-trade-manager]
url = "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "amitblecher-trade-manager": {
      "type": "remote",
      "url": "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add amitblecher-trade-manager --url 'https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  amitblecher-trade-manager:
    url: "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "amitblecher-trade-manager": {
      "Transport": "http",
      "Url": "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add amitblecher-trade-manager -t streamable-http -u 'https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp'
```

### Other

```json
{
  "mcpServers": {
    "amitblecher-trade-manager": {
      "type": "http",
      "url": "https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 60, +37)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 217 → 240
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass

## MCP tools (4)

### `test_setup` (~153 tokens)

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.

Input parameters:

- `horizon_days` (integer)
- `rule` (string, required)

### `scan_today` (~123 tokens)

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.

Input parameters:

- `limit` (integer)
- `rule` (string, required)

### `rule_language` (~28 tokens)

How to write a rule for test_setup and scan_today: the available names, operators and examples.

Output parameters:

- `result` (string)

### `what_happened_today` (~134 tokens)

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.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 62
- 2026-11-10: 61
- 2026-11-09: 61
- 2026-11-08: 61
- 2026-11-07: 60
- 2026-11-06: 23
- 2026-11-05: 23
- 2026-11-04: 59
- 2026-11-03: 59

## Common questions

### What is the io.github.amitblecher/trade-manager MCP server?

io.github.amitblecher/trade-manager is an MCP server listed in the public MCP registry as io.github.amitblecher/trade-manager. Backtest any trading setup on the S&P 500 vs random days, and see which stocks matched today. This page covers its hosted endpoint (https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp).

### Is the io.github.amitblecher/trade-manager MCP server safe to use?

io.github.amitblecher/trade-manager scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.amitblecher/trade-manager MCP server expose?

io.github.amitblecher/trade-manager exposes 4 tools: test_setup, scan_today, rule_language, what_happened_today. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.

### Does the io.github.amitblecher/trade-manager MCP server require authentication?

No. We connected to io.github.amitblecher/trade-manager without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.amitblecher/trade-manager MCP server still maintained?

io.github.amitblecher/trade-manager is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.amitblecher/trade-manager MCP server?

VerifyMCP ran 12 checks on io.github.amitblecher/trade-manager, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.amitblecher/trade-manager: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp
- Website: https://trademanager.site/
- Changelog RSS feed: https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web.xml
- Changelog JSON feed: https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web.json
- HTML version of this page: https://verifymcp.io/servers/amitblecher-trade-manager/amitblecher10-trade-manager-mcp-web
