Fensory vs Composer MCP
Fensory’s hosted MCP server is active. Composer MCP’s package remains installable, but its repository returns 404, its last package release was in July 2025 and the advertised remote endpoint no longer resolves. This is therefore a current product compared with a retired or unsupported connector, not two equivalent live MCP services.
Composer itself continues to operate an automated-strategy platform. The narrow conclusion concerns the MCP connector. A reader evaluating Composer’s current product should use Composer’s own live platform information rather than treating an old directory listing as proof that its MCP server still works.
Every cell was checked against first-party documentation, governing terms or regulator material on 2026-10-18, never on a directory listing or another comparison. Fensory publishes this page and appears in the table.
Side by side
| Product | Who holds the funds | What stops a bad order | What it trades | Where you can open it |
|---|---|---|---|---|
| Composer MCPOlder connector into Composer automated strategies | Composer, in your account there | Dry-run preview tools. No cap or allow-list | US equities, ETFs and crypto through automated strategies | US |
| FensoryOursActive hosted MCP for supported market execution | You. Tokens settle to a wallet you control, perp margin sits at the venue | a kill-switch, an access expiry, a market allow-list and a per-order cap, all enforced on the account. An order above the cap is rejected rather than trimmed | MCP: Hyperliquid spot and perpetual futures. App: tokenized US equities and treasuries, and gold | Not available to US persons |
Every row uses the same custody, control, asset and geography fields so the comparison stays aligned.
What you are choosing
The operating trade-off in concrete terms, from first setup to the markets the agent can reach.
| Decision | Composer MCP | Fensory |
|---|---|---|
| MCP status | Package exists; server appears retired | Active hosted endpoint |
| Primary workflow | Automated strategy construction | Account and market tools in an assistant |
| Credentials | API key and secret | OAuth |
| Preview | Dry-run tools were documented | Read first, prepare and verify order state |
| Geography | US product | Eligible non-US users |
Where it is stronger
Specific rather than generous. A comparison that cannot name what the other product does better has not understood it.
Composer MCP
Composer’s broader product is stronger for a US customer whose main job is expressing, backtesting and automating a rules-based portfolio strategy. The old MCP connector reflected that strategy-first model and included dry-run previews. Fensory does not provide Composer’s visual strategy construction or its historical backtesting environment, and this page does not turn a connector-status finding into a criticism of Composer’s live platform.
What connecting actually involves
Composer MCP
The public Python package can still be found, but the linked source repository and advertised endpoint did not resolve when checked. A directory may therefore show an install command for software whose maintained service is gone. Treat the connector as unavailable unless Composer publishes a current endpoint or repository. Use Composer’s current platform directly if its strategy builder is the capability you need.
Fensory
Add the remote MCP URL to a verified client, complete browser OAuth and configure the account controls in the app. The assistant can then inspect the account and supported markets. Write actions remain subject to eligibility, product availability and the account boundary rather than a backtest result or strategy deployment engine.
Where Fensory differs
Fensory offers a live remote endpoint authorized through OAuth. The assistant can read account state, market data, orders and fills and can call supported spot and perpetual-futures tools. The client does not store a Composer-style API key and secret.
Composer centers a strategy that can be backtested and automated. Fensory centers an account that compatible assistants can inspect and operate within configured market, order and time boundaries. These are different abstractions even when both use natural language.
The geographic and instrument scope also differs. Composer serves a US brokerage workflow involving equities, ETFs and crypto strategies. Fensory is unavailable to US persons and currently executes Hyperliquid spot and perpetual futures through MCP.
Which one is for you
You want a current MCP endpoint for a supported assistant
Fensory. Composer MCP should not be selected from an old directory entry without new vendor evidence.
You want a visual rules-based strategy and backtesting product in the US
Evaluate Composer’s live platform directly. That strength does not depend on the old MCP connector.
You want OAuth instead of an API secret in the client
Fensory. Its active connector uses a browser authorization flow.
You found Composer MCP in a directory
Check the repository, release date and endpoint before installing. The listing may describe the historical connector.
Questions people ask
- Is Composer MCP still active?
- The package remains listed, but the linked repository returns 404, the last release was in July 2025 and the advertised endpoint did not resolve when checked.
- Is Composer itself shut down?
- No such claim is made. Composer’s trading platform remains a separate live product. This page evaluates the MCP connector only.
- Can Fensory backtest a Composer strategy?
- No comparable visual backtesting product is claimed. Fensory exposes account, market and order tools to compatible assistants.
- Does Fensory need an API key?
- The MCP connection uses OAuth. The user signs in through the browser rather than placing an exchange API key in the client configuration.
- Why keep a page about a retired connector?
- Because current directory listings still send readers to it. A dated status page prevents an install decision from relying on an abandoned listing.
- Is Composer MCP still an active connection?
- We found the old package, but its referenced repository and endpoint were not operating as a current supported MCP route on the verification date. The page therefore treats Composer MCP as retired rather than recommending an install that could not be reproduced.
- Does the live Composer platform prove that its MCP server works?
- No. Composer can continue operating its consumer strategy platform while an older connector is unavailable. A live company website and an installable historical package are not evidence that the endpoint an assistant needs is supported today.
How this was put together
Composer MCP status was checked against the package listing, linked repository and advertised endpoint. The page says “appears retired” because the company has not published a formal retirement notice for the connector.
The table row is held by reference in the trading MCP roundup. If Composer restores the repository or endpoint, the shared source row and this page must be updated together.
The comparison separates the connector from the company’s live platform. It does not infer product quality, account availability or business status from a missing MCP repository.
Fensory publishes this comparison. Composer receives the recommendation for its live strategy-building and backtesting workflow where that product, rather than MCP, answers the reader’s need.