mcp-registry/ca.jiangzhang.api/signals-api-mcp · v1.0.0
As of 2026-10-26 19:51 UTC, the Jiangzhang Signals Api MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Daily AI signals for agents: today's 4 signals, what changed, ranked models and repos
Point your MCP client at this streamable-http endpoint: https://data.jiangzhang.ca/signals4/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 →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fca.jiangzhang.api%2Fsignals-api-mcp/fixes
{
"name": "archive_days",
"description": "List the archived daily editions (dates) available from the free digest. Use to find which dates can be cited.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}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/ca.jiangzhang.api/signals-api-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ca.jiangzhang.api/signals-api-mcp"}) over MCP.
top_models ~95 tokensdaily_signals ~92 tokenswhat_changed ~84 tokenstop_repos ~83 tokensarchive_days ~64 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%2Fca.jiangzhang.api%2Fsignals-api-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fca.jiangzhang.api%2Fsignals-api-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fca.jiangzhang.api%2Fsignals-api-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fca.jiangzhang.api%2Fsignals-api-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fca.jiangzhang.api%2Fsignals-api-mcp?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:91ba4d9b5ebee9e9…, first seen 2026-10-17, included at leaf 15048 of 75,121. Version history · verify what your client received.
Compare: most reliable knowledge 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-26 19:51 UTC, the Jiangzhang Signals Api MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Jiangzhang Signals Api MCP server advertises 5 tools, including archive_days, daily_signals, top_models, top_repos, what_changed.
Point your MCP client at this streamable-http endpoint: https://data.jiangzhang.ca/signals4/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.