Is the Skalinin909 Tradingcalc MCP server down?

mcp-registry/io.github.skalinin909/tradingcalc · v2.14.0

Also listed as glama/skalinin909/tradingcalc-mcp-server

healthy
Last checked 2026-10-20 03:05 UTC · handshake 235ms

As of 2026-10-20 03:05 UTC, the Skalinin909 Tradingcalc MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.9%
checks observed
3,923
outages (90d)
4
tools
76

Deterministic crypto futures, on-chain risk, and prediction-market math. 32 tools. Not AI estimates.

Install Skalinin909 Tradingcalc MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http skalinin909-tradingcalc-mcp-server https://tradingcalc.io/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "skalinin909-tradingcalc-mcp-server": {
      "type": "http",
      "url": "https://tradingcalc.io/api/mcp"
    }
  }
}

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

Agent-readiness: D (64/100)

D (64/100): 0 error(s), 6 warning(s) across 76 tool(s); ~24,051 tokens of tool definitions.
Scores higher than 1% of 15,385 MCP servers Glimind has audited.
Its tool list costs an agent ~24,051 tokens per session — more than 95% of servers.
64 → 64 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions69
Safety hints100
Token cost35
Client compatibility20
Protocol40
Reliability85
Stability20

What to fix (8)

76 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

76 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: primitive.average_entry, primitive.hedge_ratio, system.pubkey, system.verify, workflow.run_average_down and 71 more

34 parameter(s) across 23 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: primitive.average_entry, workflow.run_average_down, workflow.run_breakeven_planning, workflow.run_covered_call_protective_put, workflow.run_dca_entry and 18 more

Loading this server's tool list costs an agent ~24,051 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Negotiates MCP 2024-11-05. 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 →

Handshake + tools/list takes ~1,803 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.

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 →

In the last 30 days: 0 tool(s) removed and 29 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: 76 corrected tool definitions

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

primitive.average_entry 1 change
{
  "name": "primitive_average_entry",
  "description": "Calculate the weighted average entry price from multiple buy/sell fills (DCA): the bare number only, no breakeven or per-fill breakdown. Use when user asks only \"what's my average entry?\" and wants just that figure. For breakeven and a per-level summary too, use workflow.run_dca_entry instead. Returns: averagePrice, totalSize, totalCost.",
  "inputSchema": {
    "type": "object",
    "required": [
      "symbol",
      "input"
    ],
    "properties": {
      "input": {
        "type": "object",
        "required": [
          "fills"
        ],
        "properties": {
          "fills": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "price",
                "quantity"
              ],
              "properties": {
                "price": {
                  "type": "number",
                  "description": "Fill price"
                },
                "quantity": {
                  "type": "number",
                  "description": "Fill quantity"
                }
              }
            },
            "minItems": 1
          }
        }
      },
      "symbol": {
        "type": "string",
        "description": "Trading pair symbol, e.g. BTCUSDT"
      },
      "contractType": {
        "enum": [
          "linear",
          "inverse"
        ],
        "type": "string",
        "description": "linear = USDT-margined, average is the arithmetic mean (default). inverse = coin-margined, average is the harmonic mean (fill quantity is USD notional)."
      },
      "exchangeCode": {
        "type": "string",
        "description": "Exchange identifier (optional)"
      }
    }
  },
  "annotations": {
    "title": "Average Entry Price",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  },
  "title": "Average Entry Price"
}
primitive.hedge_ratio 1 change
{
  "name": "primitive_hedge_ratio",
  "description": "Calculate the short perpetual futures position size needed to hedge a spot holding. Use when user asks \"how much should I short to hedge my BTC?\" or \"what margin do I need for a 100% hedge?\". Returns: hedgeNotional, requiredMargin, estimatedFundingCost.",
  "inputSchema": {
    "type": "object",
    "required": [
      "spotSize"
    ],
    "properties": {
      "leverage": {
        "type": "number",
        "description": "Leverage on the perp short. Default 1."
      },
      "spotSize": {
        "type": "number",
        "description": "Spot position value in USDT"
      },
      "hedgeRatio": {
        "type": "number",
        "description": "Percentage of spot to hedge, e.g. 100 for full hedge, 50 for half. Default 100."
      },
      "fundingRatePct": {
        "type": "number",
        "description": "Current 8h funding rate as percentage, e.g. 0.01. Used for cost estimate."
      }
    }
  },
  "annotations": {
    "title": "Hedge Ratio",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  },
  "title": "Hedge Ratio"
}
system.pubkey 1 change
{
  "name": "system_pubkey",
  "description": "Return the ECDSA P-256 public key (PEM + JWK) and canonical signing format used to sign tool responses, so results can be verified offline without calling back to TradingCalc. Every tools/call result includes a signed second content block when signing is configured; also available at GET /api/mcp/pubkey.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {}
  },
  "annotations": {
    "title": "Signing Public Key",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  },
  "title": "Signing Public Key"
}

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

Agents: watch_tool({"toolId": "mcp-registry/io.github.skalinin909/tradingcalc"}) 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.skalinin909%2Ftradingcalc.svg)](https://glimind.com/server/mcp-registry%2Fio.github.skalinin909%2Ftradingcalc?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.skalinin909%2Ftradingcalc?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.skalinin909%2Ftradingcalc.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.skalinin909%2Ftradingcalc.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.skalinin909%2Ftradingcalc?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:8f4ced94f8c8d8bb…, first seen 2026-10-17, included at leaf 16424 of 30,377. Version history · verify what your client received.

Tools (76)

Compare: most reliable finance servers · most reliable security servers · most reliable devops 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 Skalinin909 Tradingcalc MCP server down right now?

As of 2026-10-20 03:05 UTC, the Skalinin909 Tradingcalc MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Skalinin909 Tradingcalc MCP server provide?

Skalinin909 Tradingcalc MCP server advertises 76 tools, including primitive.average_entry, primitive.hedge_ratio, system.pubkey, system.verify, workflow.run_average_down.

How do I install Skalinin909 Tradingcalc MCP server?

Point your MCP client at this streamable-http endpoint: https://tradingcalc.io/api/mcp

Is the Skalinin909 Tradingcalc MCP server safe to connect to an AI agent?

Glimind scanned all 76 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 Skalinin909 Tradingcalc 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