Zhiji Signal

run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeasPublished by x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.runOfficial publisherv3.20.1Updated Oct 24, 2026

Market phase transition signals for HS300 and BTC via MCP

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint that surfaces market phase transition signals for the HS300 index and BTC, letting an assistant query regime-change signals.

What you can do
  • Retrieve market phase transition signals for HS300 and BTC.
  • The manifest lists no individual tools, so the exact queries and output format are not documented.
  • Access is through a single remote streamable HTTP endpoint.
When to use it
Worth adding when you want an assistant to pull phase or regime transition signals for the Chinese HS300 index and Bitcoin, for example while discussing market timing or regime shifts.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The manifest declares no authentication, and no account or API key setup is documented.
Before you install
The server provides market signals that could inform financial decisions; treat them as informational rather than advice. No authentication is declared, so anyone with the endpoint can likely reach it, and no documentation describes what data is logged or sent onward.

Installation

In SourceWeft

  1. Open Zhiji Signal in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas%2Fzhiji-signal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zhiji-signal": {
      "type": "http",
      "url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v3.20.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.