MCPify
REMOTE · MCP.MCPIFY.TRADE
Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution
Available components
Last scanned (20 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability49
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1916 tokens (~51/item across 37 items; 17 tools + 20 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
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 →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- Resource “proposal-view-v” now points somewhere else: ui://mcpfutures/proposal.html?v=be6ef2e3c5 → ui://mcpfutures/proposal.html?v=059111a61e security
- Tool “preview_order” rewrote its description, which is the text the model reads security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Oct 26 0
- Schema quality: 41 → 50 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “get_my_deposit_addresses” functional
- New tool “get_my_deposits” functional
- New tool “preview_deposit” functional
- 12 Oct 26 0
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Tool “set_position_tp_sl” rewrote its description, which is the text the model reads security
- Schema quality: 37 → 41 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_my_positions” functional
- “set_position_tp_sl” reworded the description of “stop_loss” cosmetic
- “set_position_tp_sl” reworded the description of “take_profit” cosmetic
- 1 Oct 26 0
- Stability: 0.97 → pass security
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://mcp.mcpify.trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpify.trade | CN=WE1,O=Google Trust Services,C=US | 16 Nov 2026 | 14 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | cd39ae0e0afa3c660e26033aade0c92e |
| SANs: mcpify.trade, *.mcpify.trade | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.mcpify.trade. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| trade. | DS published | 64969 | 8 | Verified |
| mcpify.trade. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.mcpify.trade/.well-known/oauth-protected-resource/mcp", scope="mcp.read mcp.trade"
Bearer resource_metadata="https://mcp.mcpify.trade/.well-known/oauth-protected-resource/mcp", scope="mcp.read mcp.trade" Protected resource metadata
| Document | https://mcp.mcpify.trade/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.mcpify.trade/mcp |
| Authorisation server | https://api.mcpify.trade |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mcpify.trade/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.mcpify.trade/mcp | Inconclusive | 404 |
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 →
cancel_order ~56
Use this when the user asks to cancel a resting or trigger order by its oid (from get_my_open_orders).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | The Hyperliquid order id (oid) to cancel — see get_my_open_orders |
No output schema declared.
No examples provided.
close_position ~78
Use this when the user asks to close (fully or partially) an open Hyperliquid position. Risk-reducing: works whenever agent trading is armed.
| Name | Type | Req | Description |
|---|---|---|---|
| size | number | – | Partial close size in coins. Omit to close the entire position |
| symbol | string | yes | Coin symbol of the open position, e.g. BTC |
No output schema declared.
No examples provided.
get_candles ~68
Use this when the user wants OHLCV candle history for a Hyperliquid perp market (for analysis or charting).
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Candle interval |
| limit | integer | – | Number of candles |
| symbol | string | yes | Coin symbol, e.g. BTC |
No output schema declared.
No examples provided.
get_markets ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows |
| search | string | – | Filter by symbol substring, e.g. BTC |
| sort | string | – | Sort order |
No output schema declared.
No examples provided.
get_my_account ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_my_deposit_addresses ~101
Use this when the user asks how to deposit or fund their MCPify / Hyperliquid account. Returns THEIR personal deposit addresses (USDC or ETH on Arbitrum One, USDC or SOL on Solana) with minimums, fees and arrival times; everything sent there is credited to the user's own Hyperliquid account. Read-only: it never moves money, and there is no withdraw tool. Give the user only these exact addresses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_my_deposits ~118
Use this when the user says they sent a deposit or asks where their money is. Lists their deposits in progress (each step, and exactly what to send if one is waiting below the minimum) and their recent finished deposits (sent → swapped → fee → credited). Calling it also makes MCPify check the user's deposit addresses every few seconds for the next few hours, so a fresh transfer shows up fast.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many finished deposits to include, newest first. Deposits still in progress are always all listed |
No output schema declared.
No examples provided.
get_my_open_orders ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_my_order_records ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter by action |
| limit | integer | – | Number of records |
No output schema declared.
No examples provided.
get_my_positions ~115
Use this when the user asks about their open positions, or before closing a position or moving its stop-loss / take-profit. Returns each position's side, size, entry, mark and liquidation price, leverage, margin, unrealized PnL, and the take-profit and stop-loss orders protecting it right now (with their order ids). Pass symbol for one coin.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Only the position in this coin, e.g. BTC, SOL, xyz:TSLA. Omit for every open position. |
No output schema declared.
No examples provided.
get_my_trade_history ~53
Use this when the user asks for their recent fills/executions on Hyperliquid (live venue truth: price, size, fee, realized PnL).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of fills |
No output schema declared.
No examples provided.
get_orderbook ~57
Use this when the user wants the live order book (bids/asks) for a Hyperliquid perp market.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Levels per side |
| symbol | string | yes | Coin symbol, e.g. BTC |
No output schema declared.
No examples provided.
get_price ~68
Use this when the user asks the current price of a specific coin on Hyperliquid (mark price, 24h change, volume, funding).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Hyperliquid perp coin symbol, e.g. BTC, ETH, xyz:TSLA (not BTCUSDT) |
No output schema declared.
No examples provided.
place_order ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| leverage | integer | – | Leverage multiplier |
| limit_price | number | – | Required when order_type is limit |
| margin_mode | string | – | Margin mode |
| margin_usd | number | yes | USDC margin to commit. Position notional = margin × leverage |
| order_type | string | – | Execution type |
| side | string | yes | Position direction |
| stop_loss | number | – | Stop-loss trigger price |
| symbol | string | yes | Hyperliquid perp coin symbol, e.g. BTC, ETH, SOL (not BTCUSDT) |
| take_profit | number | – | Take-profit trigger price |
No output schema declared.
No examples provided.
preview_deposit ~241
Use this when the user wants to deposit a specific amount: returns the exact address to send it to and how much USDC will be credited to their own Hyperliquid account (exact for USDC; for ETH/SOL an estimate at today's price plus a guaranteed minimum; after Hyperliquid's one-time 1 USDC activation fee on a first deposit) — or explains why an amount is below the minimum. Read-only: nothing is sent, reserved or signed. After the user sends, call get_my_deposits to follow it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | How much of that asset the user plans to send, in the asset's own units (100 = 100 USDC, 0.05 = 0.05 ETH) |
| asset | string | yes | What the user will send. USDC on Arbitrum must be native USDC (not USDC.e); USDT is not accepted |
| network | string | yes | The network the user sends on: arbitrum = Arbitrum One, solana = Solana. USDC works on both, ETH only on arbitrum, SOL only on solana |
No output schema declared.
No examples provided.
preview_order ~260
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. It also says what the account still needs before place_order can go through (agent trading off, no approved trading agent, or the one-time platform-fee approval): relay that to the user and wait for them instead of calling place_order. If the user confirms, call place_order with the same arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| leverage | integer | – | Leverage multiplier |
| limit_price | number | – | Required when order_type is limit |
| margin_mode | string | – | Margin mode |
| margin_usd | number | yes | USDC margin to commit. Position notional = margin × leverage |
| order_type | string | – | Execution type |
| side | string | yes | Position direction |
| stop_loss | number | – | Stop-loss trigger price |
| symbol | string | yes | Hyperliquid perp coin symbol, e.g. BTC, ETH, SOL (not BTCUSDT) |
| take_profit | number | – | Take-profit trigger price |
No output schema declared.
No examples provided.
set_position_tp_sl ~142
Use this when the user asks to set or move the take-profit and/or stop-loss of an open Hyperliquid position. Only the legs you pass change: passing just stop_loss moves the stop and keeps the current take-profit (and vice versa). To remove a leg, cancel its order id from get_my_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_loss | number | – | New stop-loss trigger price. Omit to leave the current stop-loss as it is |
| symbol | string | yes | Coin symbol of the open position, e.g. BTC |
| take_profit | number | – | New take-profit trigger price. Omit to leave the current take-profit as it is |
No output schema declared.
No examples provided.
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.
remote · mcp.mcpify.trade
claude mcp add --transport http trade-mcpify-mcpify 'https://mcp.mcpify.trade/mcp'
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 82 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 17 tools: get_markets, get_price, get_orderbook, get_candles, get_my_account, and 12 more. Their descriptions and schemas cost roughly 1,804 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 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 MCPify MCP server?
VerifyMCP ran 13 checks on MCPify, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about MCPify: HTTPS. 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.