Composer Trade MCP Server

composer-trade-mcp PyPI v0.1.7

Published by invest-composer — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Composer MCP Server - Backtest and Automate your trades with LLMs

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 26

Each tool and what it can reach — statically extracted from the published source.

  • backtest_symphonyno sensitive capability
  • backtest_symphony_by_idno sensitive capability
  • cancel_invest_or_withdrawno sensitive capability
  • cancel_single_tradeno sensitive capability
  • copy_symphonyno sensitive capability
  • create_symphonyno sensitive capability
  • execute_single_tradeno sensitive capability
  • get_account_holdingsno sensitive capability
  • get_aggregate_portfolio_statsno sensitive capability
  • get_aggregate_symphony_statsno sensitive capability
Show 16 more tools ↓
  • get_market_hoursno sensitive capability
  • get_portfolio_daily_performanceno sensitive capability
  • get_saved_symphonyno sensitive capability
  • get_symphony_daily_performanceno sensitive capability
  • go_to_cash_for_symphonyno sensitive capability
  • invest_in_symphonyno sensitive capability
  • liquidate_symphonyno sensitive capability
  • list_accountsno sensitive capability
  • preview_rebalance_for_symphonyno sensitive capability
  • preview_rebalance_for_userno sensitive capability
  • rebalance_symphony_nowno sensitive capability
  • save_symphonyno sensitive capability
  • search_symphoniesno sensitive capability
  • skip_automated_rebalance_for_symphonyno sensitive capability
  • update_saved_symphonyno sensitive capability
  • withdraw_from_symphonyno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.7 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/composer-trade-mcp/badge.svg)](https://mcptrustchecker.com/registry/composer-trade-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/composer-trade-mcp"><img src="https://mcptrustchecker.com/registry/composer-trade-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/composer-trade-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan composer-trade-mcp --online --registry pypi

Use the free API → How scoring works

More in Security & Testing