mcp-registry/com.run402.zhiji-daily-report/zhiji-signal · v5.3.3
As of 2026-10-27 03:06 UTC, the Run402 Zhiji Daily Report Zhiji Signal MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.1 hours.
Daily A-share market brief with LG phase signals. No auth required.
Point your MCP client at this streamable-http endpoint: https://zhiji-daily-report.run402.com/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.run402.zhiji-daily-report/zhiji-signal"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.run402.zhiji-daily-report/zhiji-signal"}) over MCP.
phase-signal ~62 tokenssignal-latest ~58 tokensji-sensing ~55 tokensdaily-brief ~48 tokensarena-signal ~47 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.run402.zhiji-daily-report%2Fzhiji-signal?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.run402.zhiji-daily-report%2Fzhiji-signal?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.run402.zhiji-daily-report%2Fzhiji-signal.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.run402.zhiji-daily-report%2Fzhiji-signal.svg :target: https://glimind.com/server/mcp-registry%2Fcom.run402.zhiji-daily-report%2Fzhiji-signal?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0ef0580e50df11fb…, first seen 2026-10-17, included at leaf 3681 of 77,001. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:06 UTC, the Run402 Zhiji Daily Report Zhiji Signal MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.1 hours.
Run402 Zhiji Daily Report Zhiji Signal MCP server advertises 5 tools, including arena-signal, daily-brief, ji-sensing, phase-signal, signal-latest.
Point your MCP client at this streamable-http endpoint: https://zhiji-daily-report.run402.com/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.