Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+4 this week 67 Trust /100

Last scanned (17 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 8 Nov 26 +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.

  • 7 Nov 26 +37
    • Injection markers: unverified → pass ▲ security
    • 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 security
    • Schema quality: 217 → 240 ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.13 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.us-east.modal.run CN=YE2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA384 63abab4602edde2276922ebe98ae22cff88
SANs: *.us-east.modal.run
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of amitblecher10--trade-manager-mcp-web.us-east.modal.run. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
run. DS published 20657 8 Verified
modal.run. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp Verified 200
http (plaintext) http://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp HTTPS enforced 308 https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp
MCP tools · 4 exposed · ~438 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
rule_language ~28

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

scan_today ~123

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.

NameTypeReqDescription
limitinteger––
rulestringyes–

No output schema declared.

No examples provided.

test_setup ~153

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.

NameTypeReqDescription
horizon_daysinteger––
rulestringyes–

No output schema declared.

No examples provided.

what_happened_today ~134

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.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

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.

remote · amitblecher10--trade-manager-mcp-web.us-east.modal.run

# add to Claude Code
claude mcp add --transport http amitblecher-trade-manager 'https://amitblecher10--trade-manager-mcp-web.us-east.modal.run/mcp'
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.