run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-signal
REMOTE · X-API-ZHIJI-SIGNAL-FBLFAYYEAS.CN-SHANGHAI.FCAPP.RUN · SCANNED SEP 20
Market phase transition signals for HS300 and BTC via MCP
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… MCP server?
run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… is a hosted endpoint at https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run
claude mcp add --transport http run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy 'https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp'
{
"mcpServers": {
"run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy": {
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
} {
"servers": {
"run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy": {
"type": "http",
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
} [mcp_servers.run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy] url = "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy": {
"type": "remote",
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp",
"enabled": true
}
}
} openclaw mcp add run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy --url 'https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp' --transport streamable-http
mcp_servers:
run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy:
url: "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp" {
"McpServers": {
"run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy": {
"Transport": "http",
"Url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
} assistant mcp add run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy -t streamable-http -u 'https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp'
{
"mcpServers": {
"run-fcapp-cn-shanghai-x-api-zhiji-signal-fblfayy": {
"type": "http",
"url": "https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fcapp.run,O=Alibaba (China) Technology Co.\, Ltd.,L=Hangzhou,ST=Zhejiang,C=CN | CN=GlobalSign GCC R46 OV TLS CA 2025,O=GlobalSign nv-sa,C=BE | 28 Aug 2026 | 15 Mar 2027 | RSA 2048 | SHA256-RSA | 6507bba947f939437ffb7d3b |
| SANs: *.fcapp.run, *.accelerate.cn-hongkong.fcapp.run, *.ap-northeast-1-internal.fcapp.run, *.ap-northeast-1-vpc.fcapp.run, *.ap-northeast-1.fcapp.run, *.ap-northeast-2-internal.fcapp.run, *.ap-northeast-2-vpc.fcapp.run, *.ap-northeast-2.fcapp.run, *.ap-south-1-internal.fcapp.run, *.ap-south-1-vpc.fcapp.run, *.ap-south-1.fcapp.run, *.ap-southeast-1-internal.fcapp.run and 89 more | ||||||
| CN=GlobalSign GCC R46 OV TLS CA 2025,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE | 17 Sept 2025 | 23 Jun 2029 | RSA 2048 | SHA256-RSA | 84435890836f67394182cb9c9a5dc99f |
| CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 20 Nov 2019 | 28 Jan 2028 | RSA 4096 | SHA384-RSA | 75a8bad68321350b5b0bac34e1ce389f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| fcapp.run. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp | Auth required | 403 | |
| http (plaintext) | http://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp | Inconclusive | 403 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
What is the run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… MCP server?
run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… is an MCP server listed in the public MCP registry as run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s…. Market phase transition signals for HS300 and BTC via MCP. This page covers its hosted endpoint (https://x-api-zhiji-signal-fblfayyeas.cn-shanghai.fcapp.run/mcp).
Is the run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… MCP server safe to use?
run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… scores 28 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… MCP server require authentication?
Yes. run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… MCP server still maintained?
run.fcapp.cn-shanghai.x-api-zhiji-signal-fblfayyeas/zhiji-s… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.