MCPify
REMOTE · MCP.MCPIFY.TRADE · SCANNED SEP 25
Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution
Available components
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability48
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1240 tokens (~37/item across 33 items; 13 tools + 20 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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'
{
"mcpServers": {
"trade-mcpify-mcpify": {
"url": "https://mcp.mcpify.trade/mcp"
}
}
} {
"servers": {
"trade-mcpify-mcpify": {
"type": "http",
"url": "https://mcp.mcpify.trade/mcp"
}
}
} [mcp_servers.trade-mcpify-mcpify] url = "https://mcp.mcpify.trade/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trade-mcpify-mcpify": {
"type": "remote",
"url": "https://mcp.mcpify.trade/mcp",
"enabled": true
}
}
} openclaw mcp add trade-mcpify-mcpify --url 'https://mcp.mcpify.trade/mcp' --transport streamable-http
mcp_servers:
trade-mcpify-mcpify:
url: "https://mcp.mcpify.trade/mcp" {
"McpServers": {
"trade-mcpify-mcpify": {
"Transport": "http",
"Url": "https://mcp.mcpify.trade/mcp"
}
}
} assistant mcp add trade-mcpify-mcpify -t streamable-http -u 'https://mcp.mcpify.trade/mcp'
{
"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.
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.
- 25 Sept 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
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
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 25 Sept 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 | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3fe0d5bbd708e318139782cefb74c277 |
| 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. | present | 64969 | 8 | Verified |
| mcpify.trade. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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_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_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_order ~212
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.
| 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 ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_loss | number | – | New stop-loss trigger price |
| symbol | string | yes | Coin symbol of the open position, e.g. BTC |
| take_profit | number | – | New take-profit trigger price |
No output schema declared.
No examples provided.
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.