Zhiji Signal is the official remote MCP server from fcapp.run. It answers at https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp over streamable HTTP and asks you to sign in with your fcapp.run account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, got the sign-in challenge, so it is up.
Market phase transition signals for HS300 and BTC via MCP
Description as the publisher wrote it.
A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your fcapp.run account, and the tools appear once you have approved it.
Every block below points at https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp. Pick your client and copy.
claude mcp add --transport http zhiji-signal https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp
{
"mcpServers": {
"zhiji-signal": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"]
}
}
}{
"mcpServers": {
"zhiji-signal": {
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}{
"servers": {
"zhiji-signal": {
"type": "http",
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}{
"context_servers": {
"zhiji-signal": {
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}{
"mcpServers": {
"zhiji-signal": {
"serverUrl": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}{
"mcpServers": {
"zhiji-signal": {
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}name: Zhiji Signal
version: 0.0.1
schema: v1
mcpServers:
- name: Zhiji Signal
type: streamable-http
url: https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp{
"mcpServers": {
"zhiji-signal": {
"httpUrl": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}{
"mcpServers": {
"zhiji-signal": {
"type": "http",
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}{
"mcpServers": {
"zhiji-signal": {
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fx-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run%2Fmcp&type=streamable_http&id=zhiji-signal&name=Zhiji%20Signal
It answered our last check on 24 October 2026 in 547 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by fcapp.run and served from x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run, the vendor's own domain: https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp.
Add the server with a setup above. The first time your client connects it opens the sign-in page for fcapp.run; approve it and the tools load.
It answered our last check on 24 October 2026 in 547 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.
Publisher: run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas. Endpoint host: x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run. ARD identifier: urn:air:run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas:mcp:zhiji-signal.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.