mcp-registry/io.github.skalinin909/tradingcalc · v2.15.0
Also listed as glama/skalinin909/tradingcalc-mcp-server
As of 2026-10-23 14:57 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 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.
Deterministic crypto futures, on-chain risk, and prediction-market math. 32 tools. Not AI estimates.
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.
77 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 →
77 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 →
Loading this server's tool list costs an agent ~26,120 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 →
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 52 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.skalinin909%2Ftradingcalc/fixes
{
"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. Each fill is { price, quantity } here (workflow.run_dca_entry calls the same field size). 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,
"description": "Buy/sell fills to average, each with a price and a quantity (at least 1)"
}
},
"description": "Object with a \"fills\" array, e.g. { \"fills\": [{ \"price\": 60000, \"quantity\": 0.5 }, { \"price\": 58000, \"quantity\": 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"
}{
"name": "primitive_hedge_ratio",
"description": "Calculate the short perpetual futures position size needed to hedge a spot holding. USDT-linear only: sizes and costs are in USD, there is no contractType and no coin-margined (inverse) mode. 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"
}{
"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 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.
workflow.run_portfolio_risk ~627 tokensworkflow.run_pre_trade_check ~610 tokensworkflow.run_average_down ~551 tokensworkflow.run_odds_converter ~547 tokensworkflow.run_impermanent_loss_live ~487 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%2Fio.github.skalinin909%2Ftradingcalc?ref=badge)
<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>
.. 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
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c28b8b4a18ce9a66…, first seen 2026-10-23, included at leaf 52294 of 52,719. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable security servers · most reliable devops servers · most reliable data servers · most reliable other 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-23 14:57 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 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.
Skalinin909 Tradingcalc MCP server advertises 77 tools, including primitive.average_entry, primitive.hedge_ratio, system.pubkey, system.verify, workflow.run_average_down.
Point your MCP client at this streamable-http endpoint: https://tradingcalc.io/api/mcp
Glimind scanned all 77 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.