Is the Fizzl13 Ichimoku Signal MCP server down?

mcp-registry/io.github.fizzl13/ichimoku-signal · v1.5.1

healthy
Last checked 2026-10-22 02:45 UTC · handshake 128ms

As of 2026-10-22 02:45 UTC, the Fizzl13 Ichimoku Signal MCP server is up with a Glimind reliability score of 93/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 8 minutes.

uptime (30d checks)
100%
checks observed
3,998
outages (90d)
1
tools
8

Free Ichimoku trend; paid confluence, levels, market scan and liquidity-ranked setups via x402.

Install Fizzl13 Ichimoku Signal MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http fizzl13-ichimoku-signal-mcp-server https://ichimoku-signal.onrender.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "fizzl13-ichimoku-signal-mcp-server": {
      "type": "http",
      "url": "https://ichimoku-signal.onrender.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (93/100)

A (93/100): 0 error(s), 2 warning(s) across 8 tool(s); ~2,299 tokens of tool definitions.
Scores higher than 77% of 15,538 MCP servers Glimind has audited.
Its tool list costs an agent ~2,299 tokens per session — more than 50% of servers.
93 → 93 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints80
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability56

What to fix (3)

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 →

Tools: trade_setups

Handshake + tools/list takes ~1,531 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 11 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

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/io.github.fizzl13/ichimoku-signal"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.fizzl13/ichimoku-signal"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.fizzl13%2Fichimoku-signal.svg)](https://glimind.com/server/mcp-registry%2Fio.github.fizzl13%2Fichimoku-signal?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.fizzl13%2Fichimoku-signal?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.fizzl13%2Fichimoku-signal.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.fizzl13%2Fichimoku-signal.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.fizzl13%2Fichimoku-signal?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6cccc81b5ed5f538…, first seen 2026-10-18, included at leaf 21922 of 43,077. Version history · verify what your client received.

Tools (8)

Compare: most reliable finance servers · most reliable communication servers · most reliable data servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Fizzl13 Ichimoku Signal MCP server down right now?

As of 2026-10-22 02:45 UTC, the Fizzl13 Ichimoku Signal MCP server is up with a Glimind reliability score of 93/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 8 minutes.

How many tools does Fizzl13 Ichimoku Signal MCP server provide?

Fizzl13 Ichimoku Signal MCP server advertises 8 tools, including confluence_signal, feedback, ichimoku_signal, ichimoku_trend, market_scan.

How do I install Fizzl13 Ichimoku Signal MCP server?

Point your MCP client at this streamable-http endpoint: https://ichimoku-signal.onrender.com/mcp

Is the Fizzl13 Ichimoku Signal MCP server safe to connect to an AI agent?

Glimind scanned all 8 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.

Operator of Fizzl13 Ichimoku Signal MCP server?

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.

Feedback
Help us improve