Can Claude buy a Tesla share through the Fensory MCP server?

No. On the MCP path, TSLA resolves to a perpetual future on a Hyperliquid builder dex. It gives price exposure and does not convey a share, a dividend or ownership in Tesla. Tokenized equities shown in the Fensory app are a separate instrument.

Does Claude need my private key?

No. Claude connects over OAuth. On the current MCP path, Hyperliquid trades use a scoped signing key that can sign trades and cannot withdraw, transfer or bridge funds.

Why does the prompt ask for explicit confirmation?

It keeps this example supervised. Claude shows the symbol, side, size, price and order type so you can approve or reject that specific order. This prompt instruction is separate from Fensory account controls such as the market allow-list and per-order cap.

Can I stop Claude after connecting it?

Yes. Switch agentic trading off in Fensory to make every trading tool fail. You can also disable or remove the connector in Claude.

Does a $25 order cap mean I can lose only $25?

No. The cap limits the value of one order. It does not cap total losses or stop several allowed orders. A leveraged perpetual-futures position can also lose more than the margin committed.

Agent Skill · version 0.1.0

Let Claude trade stock futures through MCP

Verify a stock-named perpetual-futures market and prepare a bounded order through the Fensory MCP server. Inspection requests stop after read-only checks and a preview. Submission requires a separate explicit instruction and confirmation.

Download SKILL.md Read the guide

Download and review

Download the public file, review every instruction, then place it in the skills directory documented by the compatible client you use. Client-specific paths are omitted until each workflow is verified.

Download: curl -fsSL https://fensory.com/skills/claude-trade-stocks/SKILL.md -o SKILL.md

What the skill instructs

Read the account and instrument before preparing an action.
Keep the proposal inside the user's ceiling and the account's per-order cap.
Show the exact symbol, side, order type and size before a write call. Include the limit price for a limit order, or the current quote and expected execution conditions for a market order, then ask for confirmation.
Report a prepared order, submitted order and fill as three different states.

SKILL.md

---
name: fensory-stock-futures
description: Verify a stock-named perpetual-futures market and prepare a bounded order through the Fensory MCP server. Inspection requests stop after read-only checks and a preview. Submission requires a separate explicit instruction and confirmation.
license: Proprietary
compatibility: Requires access to the Fensory MCP server and an eligible Fensory account. Fensory is not available to US persons.
metadata:
  author: Fensory AG
  version: "0.1.0"
  source: "https://fensory.com/skills/claude-trade-stocks"
---

# Let Claude trade stock futures through MCP

## When to use

This guide is for an eligible Claude user who wants to test a small, explicitly confirmed stock perpetual-futures order while keeping the market and order size bounded at the account layer.

It is not a guide to buying a share, receiving a dividend or building an unattended strategy. It does not tell Claude which company to trade. The example verifies the instrument and prepares one small order for your confirmation.

## Operating rules

- Start with read tools and identify the signed-in account, market, venue and instrument before preparing an action.
- Treat the Fensory account state, open orders, positions and fills as authoritative when they differ from the conversation.
- Fensory enforces three controls on the account: a kill-switch, a market allow-list and a per-order cap. Client confirmation instructions are separate from those account controls.
- Never describe a perpetual future as a share or tokenized equity. State the instrument and its risks before discussing an order.
- Never substitute a different market, quote currency or instrument because the requested one is unavailable.
- Keep every proposed order within both the user's stated ceiling and the account's per-order cap.
- Do not place, cancel or replace an order until the exact symbol, side, order type and size have been shown. For a limit order, show the limit price. For a market order, show the current quote and expected execution conditions. The user must confirm that exact action.
- Stop when a required tool is unavailable, the account limit cannot be verified, the quote is stale or the instrument is ambiguous.

## Risk and scope

This file is operational guidance, not financial advice. Trading can lose the full amount committed. Perpetual futures use margin and can be liquidated. Spot assets can lose value. Stop if the instrument, current quote or account controls cannot be verified.

## Procedure

1. **Check that perpetual-futures trading is enabled.** Claude reads whether perpetual-futures execution is active before it discusses an order. A working OAuth connection proves the server can identify you; it does not prove this market or trading action is enabled. Tools: `get_perps_status`.
2. **Resolve the instrument.** For a stock name, the MCP tool resolves the builder-dex perpetual under a prefixed symbol such as xyz:TSLA. Claude should state that it is a derivative with no share ownership before it continues. Tools: `get_market`.
3. **Read the account before sizing anything.** The existing position, available balance and open orders change what another order would do. Reading them first also catches a duplicate order that is already resting. Tools: `get_account_state`, `get_open_orders`.
4. **Prepare one bounded order.** The order value stays below both the prompt ceiling and the account cap. Claude must show the symbol, side, order type, size and price and ask for confirmation in the client before it submits. That confirmation is a client instruction, not an account-enforced limit. Tools: `place_perps_order`.
5. **Verify the result.** A submitted order may rest, fill partly or fill completely. Claude should report the actual state rather than treating a successful tool call as proof of a completed trade. Tools: `get_order_status`, `get_fills`, `get_open_orders`.

## Request template

Use the Fensory tools to inspect xyz:TSLA as a stock perpetual future. First call get_perps_status, get_market and get_account_state. State the venue, mark price, maximum leverage, my current position, available balance, market allow-list and per-order cap. Do not describe this as a share or tokenized equity.

If the market is available and my account permits it, prepare a limit order worth no more than $25 at a price I specify. Do not change leverage or margin mode. Do not place, cancel or replace any order until you show the full order, estimated fee, liquidation risk and ask for my explicit confirmation for that exact action. Stop if the symbol resolves to a different instrument, the price is stale or the order would exceed an account limit.

## Failure handling

- **The ticker hides the instrument:** TSLA can refer to a tokenized equity in the app and a perpetual future over MCP. The prompt forces Claude to identify the instrument before any order, because the custody, fees and risks are different.
- **The price moves while you review:** A mark price or order book is a snapshot. Use a limit order when the exact price matters, then re-read the market if the confirmation takes long enough for the quote to become stale.
- **The order fills partly:** A partial fill leaves both a position and a resting remainder. Read the fill and open-order records before deciding whether to leave, cancel or replace anything.
- **Margin creates liquidation risk:** A small order can still be liquidated when it is leveraged. The prompt tells Claude not to change leverage and to state the liquidation risk before asking for confirmation.
- **One cap is not a daily loss limit:** The Fensory cap applies to a single order. It does not stop several permitted orders from losing money. Keep the example supervised and use the kill-switch when you want all trading tools to stop.

## Response contract

Report the account used, the exact instrument, the tools called, the controls that applied and the current order or position state. Separate a prepared order from a submitted order, and a submitted order from a fill. If no action was taken, say so directly.

## Sources

- [Anthropic: custom connectors with remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
- [Fensory perpetual futures](https://fensory.com/markets/perps)
- [Fensory account controls](https://fensory.com/security)

Product behavior and client permissions verified 2026-10-13.

Questions people ask

Can Claude buy a Tesla share through the Fensory MCP server?: No. On the MCP path, TSLA resolves to a perpetual future on a Hyperliquid builder dex. It gives price exposure and does not convey a share, a dividend or ownership in Tesla. Tokenized equities shown in the Fensory app are a separate instrument.
Does Claude need my private key?: No. Claude connects over OAuth. On the current MCP path, Hyperliquid trades use a scoped signing key that can sign trades and cannot withdraw, transfer or bridge funds.
Why does the prompt ask for explicit confirmation?: It keeps this example supervised. Claude shows the symbol, side, size, price and order type so you can approve or reject that specific order. This prompt instruction is separate from Fensory account controls such as the market allow-list and per-order cap.
Can I stop Claude after connecting it?: Yes. Switch agentic trading off in Fensory to make every trading tool fail. You can also disable or remove the connector in Claude.
Does a $25 order cap mean I can lose only $25?: No. The cap limits the value of one order. It does not cap total losses or stop several allowed orders. A leveraged perpetual-futures position can also lose more than the margin committed.

Important information

Fensory does not provide investment advice or recommendations, does not generate buy or sell signals, and does not solicit any transaction. It supplies market data and software tooling only; all trading decisions are made by you or by an agent you configure and operate. Fensory’s fees, where charged, are published and paid by the user: a builder fee between 0.01% and 0.05% on perpetual futures and Hyperliquid spot, and no Fensory fee on tokenized equities, yields or bridging. The fee is set in advance and does not depend on the outcome of a trade.

Strategies run inside your own agent and execute only while that agent is running, only within the per-trade limits and allowed markets you set. Pre-IPO exposure is in development, with timelines subject to change. Third-party costs such as network fees and venue or issuer spreads apply. Tickers, prompts, strategies and execution examples shown on this page are illustrative only and are not recommendations; past performance of any strategy or trader does not guarantee future results.

All trading carries risk, including total loss of capital. Perpetual futures and leveraged products carry substantially higher risk and can lose more than the initial margin committed. Digital and tokenized assets may be volatile, illiquid, or subject to regulatory change.