Is the Gigshow Decker MCP server down?

mcp-registry/io.github.gigshow/decker · v0.2.0

Also listed as glama/gigshow/decker

healthy
Last checked 2026-10-23 01:47 UTC · handshake 368ms

As of 2026-10-23 01:47 UTC, the Gigshow Decker MCP server is up with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 77 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
98.9%
checks observed
4,392
outages (90d)
77
tools
14

Deterministic market-state engine for trading agents — state, gate, coordinates, with receipts.

Install Gigshow Decker MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http gigshow-decker-mcp-server https://api.decker-ai.com/api/v1/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "gigshow-decker-mcp-server": {
      "type": "http",
      "url": "https://api.decker-ai.com/api/v1/mcp"
    }
  }
}

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

Agent-readiness: D (64/100)

D (64/100): 0 error(s), 7 warning(s) across 14 tool(s); ~3,737 tokens of tool definitions.
Scores higher than 1% of 15,587 MCP servers Glimind has audited.
Its tool list costs an agent ~3,737 tokens per session — more than 55% of servers.
66 → 64 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions65
Safety hints0
Token cost100
Client compatibility50
Protocol100
Reliability60
Stability54

What to fix (7)

14 of 14 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 →

Tools: decker.close_position, decker.get_assembly, decker.get_episodes, decker.get_market_state, decker.get_positions and 9 more

14 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: decker.close_position, decker.get_assembly, decker.get_episodes, decker.get_market_state, decker.get_positions and 9 more

5 parameter(s) across 5 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 →

Tools: decker.get_episodes, decker.get_market_state, decker.get_reading, decker.get_signals, decker.get_trigger_history

4 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: decker.close_position, decker.place_order, decker.set_skill_overlay, decker.update_protective_stops

Reachable 98.9% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Handshake + tools/list takes ~1,790 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: 3 tool(s) removed and 4 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 →

Auto-fix: 14 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.gigshow%2Fdecker/fixes

decker.close_position 2 changes
{
  "name": "decker_close_position",
  "description": "Axis③ (Order/Execution) — closes (or partially reduces) an existing position through DECKER'S OWN execution engine (see decker.place_order for what that means — same account-linkage requirement applies here for real positions). Unlike place_order, there is no crypto-6 restriction — this reduces risk, not adds it, so any symbol you actually hold (including HL-synthetic/KRX paper positions) can be closed. Mode is NOT chosen by the caller — this looks up whatever position(s) actually exist for the ",
  "inputSchema": {
    "type": "object",
    "required": [
      "symbol"
    ],
    "properties": {
      "symbol": {
        "type": "string",
        "description": "e.g. BTCUSDT, XYZ_GOLDUSD — whatever symbol you hold. Aliases resolve like other tools."
      },
      "close_fraction": {
        "type": "number",
        "default": 1,
        "maximum": 1,
        "description": "Fraction of the current position to close, 0 < x <= 1. Default 1.0 = full close. E.g. 0.5 closes half.",
        "exclusiveMinimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
decker.get_assembly 2 changes
{
  "name": "decker_get_assembly",
  "description": "THE answer for 'what is the situation and what do I do on this symbol now' — one verdict per symbol, built from the per-timeframe judgment state (CR1); no scores or weights. READ IN THIS ORDER: (1) verdict = state (direction · phase) + action: 진입 enter now (a new signal) | 유지 hold the existing stance, NOT a new entry | 청산 exit | 대기 wait; `reason` says why, `until` names the close that would change it. (2) summary_ko = ready-to-show Korean lines. (3) entry / stop / target / rr = the prices (entry",
  "inputSchema": {
    "type": "object",
    "properties": {
      "detail": {
        "type": "boolean",
        "description": "Include path / watch / story / ladders / matrix_summary (about 20KB per symbol). Default false: the answer only."
      },
      "symbol": {
        "type": "string",
        "description": "Optional symbol or alias (BTC, 비트코인, GOLD, 테슬라...). Omit for all 14 symbols."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
decker.get_episodes 2 changes
{
  "name": "decker_get_episodes",
  "description": "Price-axis EPISODE history — answers 'where did I buy/sell last time, what was the target value and the event chain then, and where did price move WITHOUT a signal (and which target values it passed = missing points)'. Read-only from the persisted event ledger (no recompute). `episodes` (newest first) = one target selection until the next: target {price, from_price, reason}, chain (primary-unit judgment events), signals {ts, side, entry, targets, resolved{status, close, bar_low, bar_high}}, left",
  "inputSchema": {
    "type": "object",
    "required": [
      "symbol",
      "timeframe"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 5,
        "maximum": 20,
        "minimum": 1,
        "description": "number of episodes"
      },
      "symbol": {
        "type": "string",
        "description": "e.g. BTCUSDT"
      },
      "timeframe": {
        "enum": [
          "30m",
          "1h",
          "4h",
          "8h",
          "1d",
          "1w"
        ],
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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.gigshow/decker"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.gigshow/decker"}) 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.gigshow%2Fdecker.svg)](https://glimind.com/server/mcp-registry%2Fio.github.gigshow%2Fdecker?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.gigshow%2Fdecker?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gigshow%2Fdecker.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gigshow%2Fdecker.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.gigshow%2Fdecker?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:933725f8335e5d9a…, first seen 2026-10-20, included at leaf 33395 of 49,319. Version history · verify what your client received.

Tools (14)

Compare: most reliable finance servers · most reliable ml servers · most reliable data servers · most reliable other 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 Gigshow Decker MCP server down right now?

As of 2026-10-23 01:47 UTC, the Gigshow Decker MCP server is up with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 77 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Gigshow Decker MCP server provide?

Gigshow Decker MCP server advertises 14 tools, including decker.close_position, decker.get_assembly, decker.get_episodes, decker.get_market_state, decker.get_positions.

How do I install Gigshow Decker MCP server?

Point your MCP client at this streamable-http endpoint: https://api.decker-ai.com/api/v1/mcp

Is the Gigshow Decker MCP server safe to connect to an AI agent?

Glimind scanned all 14 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 Gigshow Decker 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