_ registry / mcp streamable-http · checked 21m ago

MCPify

https://mcp.mcpify.trade

Registry code: 8617105d80ce48ce

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.mcpify.trade/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is MCPify live?
Yes — it answered the hub's last check (checked 21m ago). It answered 99% of checks over the last 30 days.
Is MCPify free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does MCPify have?
14 tools: get_orderbook, get_my_open_orders, get_my_order_records, preview_order, place_order, close_position, cancel_order, set_position_tp_sl, ….
Is MCPify safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 99.4%· all time 99.4%

latency
740ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 358 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
crypto & onchain trading & defi
used for
  • get hyperliquid perp prices and order book
  • place a perpetual futures order
  • close a position
  • set take profit and stop loss
  • view account positions and fills
takes → gives
data → data, payments
tools
9 reads2 changes data2 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 14 tools
14 auth-required 14 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_orderbook reads auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "depth": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Levels per side"
    },
    "symbol": {
      "type": "string",
      "description": "Coin symbol, e.g. BTC"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_my_open_orders reads auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_my_order_records reads auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "description": "Number of records"
    },
    "action": {
      "enum": [
        "open",
        "close",
        "tpsl",
        "cancel"
      ],
      "type": "string",
      "description": "Filter by action"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • preview_order reads auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol",
    "side",
    "margin_usd"
  ],
  "properties": {
    "side": {
      "enum": [
        "long",
        "short"
      ],
      "type": "string",
      "description": "Position direction"
    },
    "symbol": {
      "type": "string",
      "description": "Hyperliquid perp coin symbol, e.g. BTC, ETH, SOL (not BTCUSDT)"
    },
    "leverage": {
      "type": "integer",
      "default": 5,
      "maximum": 100,
      "minimum": 1,
      "description": "Leverage multiplier"
    },
    "stop_loss": {
      "type": "number",
      "description": "Stop-loss trigger price",
      "exclusiveMinimum": 0
    },
    "margin_usd": {
      "type": "number",
      "minimum": 1,
      "description": "USDC margin to commit. Position notional = margin × leverage"
    },
    "order_type": {
      "enum": [
        "market",
        "limit"
      ],
      "type": "string",
      "default": "market",
      "description": "Execution type"
    },
    "limit_price": {
      "type": "number",
      "description": "Required when order_type is limit",
      "exclusiveMinimum": 0
    },
    "margin_mode": {
      "enum": [
        "cross",
        "isolated"
      ],
      "type": "string",
      "default": "cross",
      "description": "Margin mode"
    },
    "take_profit": {
      "type": "number",
      "description": "Take-profit trigger price",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 69 lines
  • place_order moves money auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol",
    "side",
    "margin_usd"
  ],
  "properties": {
    "side": {
      "enum": [
        "long",
        "short"
      ],
      "type": "string",
      "description": "Position direction"
    },
    "symbol": {
      "type": "string",
      "description": "Hyperliquid perp coin symbol, e.g. BTC, ETH, SOL (not BTCUSDT)"
    },
    "leverage": {
      "type": "integer",
      "default": 5,
      "maximum": 100,
      "minimum": 1,
      "description": "Leverage multiplier"
    },
    "stop_loss": {
      "type": "number",
      "description": "Stop-loss trigger price",
      "exclusiveMinimum": 0
    },
    "margin_usd": {
      "type": "number",
      "minimum": 1,
      "description": "USDC margin to commit. Position notional = margin × leverage"
    },
    "order_type": {
      "enum": [
        "market",
        "limit"
      ],
      "type": "string",
      "default": "market",
      "description": "Execution type"
    },
    "limit_price": {
      "type": "number",
      "description": "Required when order_type is limit",
      "exclusiveMinimum": 0
    },
    "margin_mode": {
      "enum": [
        "cross",
        "isolated"
      ],
      "type": "string",
      "default": "cross",
      "description": "Margin mode"
    },
    "take_profit": {
      "type": "number",
      "description": "Take-profit trigger price",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 69 lines
  • close_position moves money auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "size": {
      "type": "number",
      "description": "Partial close size in coins. Omit to close the entire position",
      "exclusiveMinimum": 0
    },
    "symbol": {
      "type": "string",
      "description": "Coin symbol of the open position, e.g. BTC"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • cancel_order changes data auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "order_id"
  ],
  "properties": {
    "order_id": {
      "type": "integer",
      "description": "The Hyperliquid order id (oid) to cancel — see get_my_open_orders"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • set_position_tp_sl changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Coin symbol of the open position, e.g. BTC"
    },
    "stop_loss": {
      "type": "number",
      "description": "New stop-loss trigger price. Omit to leave the current stop-loss as it is",
      "exclusiveMinimum": 0
    },
    "take_profit": {
      "type": "number",
      "description": "New take-profit trigger price. Omit to leave the current take-profit as it is",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_my_account reads auth-required 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_price reads auth-required 12h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Hyperliquid perp coin symbol, e.g. BTC, ETH, xyz:TSLA (not BTCUSDT)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_my_positions auth-required 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Only the position in this coin, e.g. BTC, SOL, xyz:TSLA. Omit for every open position."
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • get_markets reads auth-required 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "sort": {
      "enum": [
        "volume",
        "change",
        "symbol"
      ],
      "type": "string",
      "default": "volume",
      "description": "Sort order"
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1,
      "description": "Max rows"
    },
    "search": {
      "type": "string",
      "description": "Filter by symbol substring, e.g. BTC"
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • get_candles reads auth-required 12h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 500,
      "minimum": 1,
      "description": "Number of candles"
    },
    "symbol": {
      "type": "string",
      "description": "Coin symbol, e.g. BTC"
    },
    "interval": {
      "enum": [
        "1m",
        "3m",
        "5m",
        "15m",
        "30m",
        "1h",
        "2h",
        "4h",
        "8h",
        "12h",
        "1d",
        "3d",
        "1w",
        "1M"
      ],
      "type": "string",
      "default": "1h",
      "description": "Candle interval"
    }
  },
  "additionalProperties": false
}
    arguments 42 lines
  • get_my_trade_history reads auth-required 3h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "description": "Number of fills"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8617105d80ce48ce.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8617105d80ce48ce/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8617105d80ce48ce/badge.svg)](https://brick.blue/agent/8617105d80ce48ce?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.