MCPify
latest · 1.0.0Non-custodial Hyperliquid perp trading: live markets, account state, user-armed order execution
- Homepage
- mcpify.trade
- MCP registry
- trade.mcpify/mcpify
Install
claude mcp add --transport http trade-mcpify-mcpify https://mcp.mcpify.trade/mcp/mcp confirms it's connected.
Or add it manually in ~/.cursor/mcp.json:
{
"mcpServers": {
"trade-mcpify-mcpify": {
"url": "https://mcp.mcpify.trade/mcp"
}
}
}In claude_desktop_config.json (Settings → Developer → Edit Config), then restart:
{
"mcpServers": {
"trade-mcpify-mcpify": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.mcpify.trade/mcp"
]
}
}
}Endpoint, any MCP client:
https://mcp.mcpify.trade/mcpCommunity score
from web signals · no reviews yet (community v3)
- Web signals (ecosystem baseline)52/100 · 100% of the weight
No reviews yet — be the first.
What the web says
Objective public usage & activity (formula v3) — the community score's web-signals input, and its own sort.
Nothing collected from GitHub yet.
No package-registry data collected yet.
Not yet found on other registries or list sites.
Quotes2
- Show HN: MCPify – Bring your MCP server ideas to life ↗
I wanted to learn more about MCPs this weekend.<p>So I built this mini-tool called MCPify.ai. It's a no-code way to bring your MCP-server ideas to life.<p>I made it in such a way that anyone will be able to create their own MCP server …
- Show HN: Mcpify – Turn any REST API into an MCP server in one command ↗
Wiring an existing API into MCP means hand-writing a tool wrapper per endpoint. Almost every API has an OpenAPI spec, so mcpify just reads it and generates the whole server. Built it because I kept doing this by hand. Feedback welcome.
- Endpoint status · 8 days ago
- Live
- Response time · 8 days ago
- 92 ms
- Listing completeness · 8 days ago
- 100%
Version history1
- 1.0.0release date unknown
Details
- Transport
- streamable-http
- Status
- listed
- Source
- Imported from the MCP registry
- Homepage
- site ↗