# MCPify (remote · mcp.mcpify.trade)

Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.mcpify.trade`: 76/100 (this document), [markdown](https://verifymcp.io/servers/trade-mcpify-mcpify/mcp.md), [page](https://verifymcp.io/servers/trade-mcpify-mcpify/mcp)

## Channel facts

- Endpoint: `https://mcp.mcpify.trade/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-09-25.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - 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**: 48/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1240 tokens (~37/item across 33 items; 13 tools + 20 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the MCPify MCP server?

MCPify is a hosted endpoint at https://mcp.mcpify.trade/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 trade-mcpify-mcpify 'https://mcp.mcpify.trade/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "trade-mcpify-mcpify": {
      "url": "https://mcp.mcpify.trade/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "trade-mcpify-mcpify": {
      "type": "http",
      "url": "https://mcp.mcpify.trade/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.trade-mcpify-mcpify]
url = "https://mcp.mcpify.trade/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trade-mcpify-mcpify": {
      "type": "remote",
      "url": "https://mcp.mcpify.trade/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add trade-mcpify-mcpify --url 'https://mcp.mcpify.trade/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  trade-mcpify-mcpify:
    url: "https://mcp.mcpify.trade/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "trade-mcpify-mcpify": {
      "Transport": "http",
      "Url": "https://mcp.mcpify.trade/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add trade-mcpify-mcpify -t streamable-http -u 'https://mcp.mcpify.trade/mcp'
```

### Other

```json
{
  "mcpServers": {
    "trade-mcpify-mcpify": {
      "type": "http",
      "url": "https://mcp.mcpify.trade/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-09-25 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 76, +1)

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

### 2026-09-22 (score 75, +1)

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

### 2026-09-20 (score 74, +1)

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

### 2026-09-18 (score 73, +1)

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

### 2026-09-15 (score 72, +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-09-13 (score 71, +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-09-11 (score 70, +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.

## MCP tools (13)

### `get_markets` (~83 tokens)

Use this when the user asks which perpetual markets are tradable on MCPify (Hyperliquid), or for a market overview with prices, 24h change, volume, funding and max leverage.

Input parameters:

- `limit` (integer): Max rows
- `search` (string): Filter by symbol substring, e.g. BTC
- `sort` (string): Sort order

### `get_price` (~68 tokens)

Use this when the user asks the current price of a specific coin on Hyperliquid (mark price, 24h change, volume, funding).

Input parameters:

- `symbol` (string, required): Hyperliquid perp coin symbol, e.g. BTC, ETH, xyz:TSLA (not BTCUSDT)

### `get_orderbook` (~57 tokens)

Use this when the user wants the live order book (bids/asks) for a Hyperliquid perp market.

Input parameters:

- `depth` (integer): Levels per side
- `symbol` (string, required): Coin symbol, e.g. BTC

### `get_candles` (~68 tokens)

Use this when the user wants OHLCV candle history for a Hyperliquid perp market (for analysis or charting).

Input parameters:

- `interval` (string): Candle interval
- `limit` (integer): Number of candles
- `symbol` (string, required): Coin symbol, e.g. BTC

### `get_my_account` (~43 tokens)

Use this when the user asks about THEIR MCPify account: balance, withdrawable, open positions with PnL and liquidation prices, and whether agent trading is armed.

### `get_my_open_orders` (~42 tokens)

Use this when the user asks for their open/resting orders on Hyperliquid (including TP/SL trigger orders). Returns each order's oid for cancellation.

### `get_my_trade_history` (~53 tokens)

Use this when the user asks for their recent fills/executions on Hyperliquid (live venue truth: price, size, fee, realized PnL).

Input parameters:

- `limit` (integer): Number of fills

### `get_my_order_records` (~69 tokens)

Use this when the user asks what orders were placed through MCPify (our audit records, including which source placed them: web, mcp agent, admin) — successes and rejections alike.

Input parameters:

- `action` (string): Filter by action
- `limit` (integer): Number of records

### `preview_order` (~212 tokens)

Use this BEFORE place_order whenever the user wants to open a position: it validates and sizes the order (fresh est. entry, size after rounding, est. liquidation, TP/SL sanity, MCP caps) WITHOUT placing anything, and shows a proposal card the user can confirm from. Read-only and always safe to call. If the user confirms, call place_order with the same arguments.

Input parameters:

- `leverage` (integer): Leverage multiplier
- `limit_price` (number): Required when order_type is limit
- `margin_mode` (string): Margin mode
- `margin_usd` (number, required): USDC margin to commit. Position notional = margin × leverage
- `order_type` (string): Execution type
- `side` (string, required): Position direction
- `stop_loss` (number): Stop-loss trigger price
- `symbol` (string, required): Hyperliquid perp coin symbol, e.g. BTC, ETH, SOL (not BTCUSDT)
- `take_profit` (number): Take-profit trigger price

### `place_order` (~210 tokens)

Use this when the user explicitly asks to open a perp position or place an order on Hyperliquid via MCPify. Real funds — ALWAYS call preview_order with the same arguments first, show the user the proposal, and get their explicit confirmation; place_order is refused unless a matching preview ran within the last 10 minutes. Requires Agent Trading enabled on the MCPify settings page.

Input parameters:

- `leverage` (integer): Leverage multiplier
- `limit_price` (number): Required when order_type is limit
- `margin_mode` (string): Margin mode
- `margin_usd` (number, required): USDC margin to commit. Position notional = margin × leverage
- `order_type` (string): Execution type
- `side` (string, required): Position direction
- `stop_loss` (number): Stop-loss trigger price
- `symbol` (string, required): Hyperliquid perp coin symbol, e.g. BTC, ETH, SOL (not BTCUSDT)
- `take_profit` (number): Take-profit trigger price

### `close_position` (~78 tokens)

Use this when the user asks to close (fully or partially) an open Hyperliquid position. Risk-reducing: works whenever agent trading is armed.

Input parameters:

- `size` (number): Partial close size in coins. Omit to close the entire position
- `symbol` (string, required): Coin symbol of the open position, e.g. BTC

### `set_position_tp_sl` (~89 tokens)

Use this when the user asks to set or update take-profit / stop-loss on an open Hyperliquid position. Replaces any existing TP/SL triggers for that coin.

Input parameters:

- `stop_loss` (number): New stop-loss trigger price
- `symbol` (string, required): Coin symbol of the open position, e.g. BTC
- `take_profit` (number): New take-profit trigger price

### `cancel_order` (~56 tokens)

Use this when the user asks to cancel a resting or trigger order by its oid (from get_my_open_orders).

Input parameters:

- `order_id` (integer, required): The Hyperliquid order id (oid) to cancel — see get_my_open_orders

## Diagnostics

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

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65

## Common questions

### What is the MCPify MCP server?

MCPify is an MCP server listed in the public MCP registry as trade.mcpify/mcpify. Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution. This page covers its hosted endpoint (https://mcp.mcpify.trade/mcp).

### Is the MCPify MCP server safe to use?

MCPify scores 76 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 MCPify MCP server expose?

MCPify exposes 13 tools: get_markets, get_price, get_orderbook, get_candles, get_my_account, and 8 more. Their descriptions and schemas cost roughly 1,128 tokens of context every time the server is loaded.

### Does the MCPify MCP server require authentication?

Yes. MCPify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the MCPify MCP server still maintained?

MCPify is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.mcpify.trade/mcp
- Authorisation metadata: https://mcp.mcpify.trade/.well-known/oauth-protected-resource/mcp
- Website: https://mcpify.trade/mcp
- Changelog RSS feed: https://verifymcp.io/servers/trade-mcpify-mcpify/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/trade-mcpify-mcpify/mcp.json
- HTML version of this page: https://verifymcp.io/servers/trade-mcpify-mcpify/mcp