mcpbeat Sign in

Shifu MCP Server

answering

Shifu is answering right now. Last checked 10 min ago.

Run TradingView-to-broker bots for futures: create, pause and edit bots, read your trade journal.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
284 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Shifu every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add mcp --transport http https://shifu.trade/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://shifu.trade/api/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://shifu.trade/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://shifu.trade/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://shifu.trade/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://shifu.trade/api/mcp streamable-http sign-in 284 ms 10 min ago

Alternatives to Shifu

same job, measured the same way
Trandence Trading Journal
by trandence

Trades, stats, playbooks and notes from your Trandence trading journal. Read-only by default.

answering
BotSpot: AI Trading, Backtests and Bots
by grzesir

AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth.

110 tools answering
Agent Trading Journal
by smizxe

AI trading journal: your agent logs trades from chart screenshots and checks your own rules.

32 installs/wk local only
Algo Trade Analytics
by algo-trade-analytics

Evidence-gated quant research for TradingView Pine Script strategies, run from your AI client.

answering
EdgeBook
by edgebook

Chart-first trading journal: log trades from notes or chart screenshots, review setups and stats.

answering
Jornalo — futures trading journal
by jornalo

Futures trading journal: performance, setups, prop-firm drawdown risk, tagging and screenshots.

answering
tradefloor
by simoncoombes

Simulated stock markets that react to your orders: run, fork and score trading agents.

804 installs/wk local only
EdgeLock Trading Journal
by edgelock

Query your trades, stats, and journal in EdgeLock and log new entries by chat. OAuth; free account.

answering

Shifu — questions

Answers built from our own checks of this server.

Why is there no tool list for Shifu?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Shifu working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 284 ms. The bar chart above shows every period we have measured.
How do I connect Shifu?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Shifu?
No API key is involved. Shifu answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Shifu?
It answers our handshake in 284 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.