Is the Kwant MCP server down?

mcp-registry/sh.kwant/kwant · v0.1.0

healthy
Last checked 2026-10-26 22:08 UTC · handshake 1.7s

As of 2026-10-26 22:08 UTC, the Kwant MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.7%
checks observed
3,687
outages (90d)
7
tools
16

Quant intelligence over MCP: backtest, signals, screens, scores & portfolios for US & TSX stocks.

Point your MCP client at this streamable-http endpoint: https://kwant.sh/mcp

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 4 warning(s) across 16 tool(s); ~4,124 tokens of tool definitions.
Scores higher than 1% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~4,124 tokens per session — more than 55% of servers.
67 → 67 since 2026-10-21
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints15
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

75 parameter(s) across 16 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: backtest, build_monthly_universe, compare_tickers, compute_correlation_matrix, compute_indicator and 11 more

16 of 16 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: backtest, build_monthly_universe, compare_tickers, compute_correlation_matrix, compute_indicator and 11 more

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

Handshake + tools/list takes ~2,406 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 →

Auto-fix: 7 corrected tool definitions

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

compare_tickers 1 change
{
  "name": "compare_tickers",
  "description": "Rank two or more tickers against each other by a single metric (total_return, volatility, sharpe, max_drawdown, last_price). Symbols that cannot be resolved (or lack enough history) are skipped and noted in `warnings` rather than failing the call. Returns a ranked list of {ticker, value, rank, currency} (rank 1 = best). (paid: $0.0050/call)",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "tickers"
    ],
    "properties": {
      "range": {
        "enum": [
          "5d",
          "1mo",
          "3mo",
          "6mo",
          "1y",
          "2y",
          "5y",
          "max"
        ],
        "type": "string",
        "default": "1y"
      },
      "metric": {
        "enum": [
          "total_return",
          "volatility",
          "sharpe",
          "max_drawdown",
          "last_price"
        ],
        "type": "string",
        "default": "total_return"
      },
      "tickers": {
        "type": "array",
        "items": {
          "type": "string"
        }
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
compute_portfolio_stats 1 change
{
  "name": "compute_portfolio_stats",
  "description": "Compute portfolio-level statistics for a weighted basket of tickers. Given a {ticker: weight} mapping, fetches each ticker's daily history over range and returns the portfolio-level (not per-ticker) volatility, sharpe, max_drawdown and total_return of the weighted basket. weights need NOT sum to 1 (normalized internally). Tickers that cannot be fetched are dropped, a note is added to warnings, and the remaining weights are renormalized. risk_free_rate is an annual rate used only by Sharpe. Retur",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "weights"
    ],
    "properties": {
      "range": {
        "enum": [
          "5d",
          "1mo",
          "3mo",
          "6mo",
          "1y",
          "2y",
          "5y",
          "max"
        ],
        "type": "string"
      },
      "weights": {
        "type": "object",
        "additionalProperties": {
          "type": "number"
        }
      },
      "risk_free_rate": {
        "type": "number"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
compute_stats 1 change
{
  "name": "compute_stats",
  "description": "Compute quantitative statistics (volatility, sharpe, max_drawdown, returns, beta, correlation) over a ticker's daily price history. Omit `metrics` to default to volatility/sharpe/max_drawdown/returns. `beta` and `correlation` require a `benchmark` ticker; `risk_free_rate` is used only by the Sharpe ratio. (paid: $0.0050/call)",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ticker"
    ],
    "properties": {
      "range": {
        "enum": [
          "5d",
          "1mo",
          "3mo",
          "6mo",
          "1y",
          "2y",
          "5y",
          "max"
        ],
        "type": "string",
        "default": "1y"
      },
      "ticker": {
        "type": "string"
      },
      "metrics": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "enum": [
                "volatility",
                "sharpe",
                "max_drawdown",
                "beta",
                "returns",
                "correlation"
              ],
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ]
      },
      "benchmark": {
        "type": [
          "string",
          "null"
        ]
      },
      "risk_free_rate": {
        "type": "number",
        "default": 0
      }
    },
    "additionalProperties": false
  },
  "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/sh.kwant/kwant"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/sh.kwant/kwant"}) 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%2Fsh.kwant%2Fkwant.svg)](https://glimind.com/server/mcp-registry%2Fsh.kwant%2Fkwant?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fsh.kwant%2Fkwant?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fsh.kwant%2Fkwant.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fsh.kwant%2Fkwant.svg
   :target: https://glimind.com/server/mcp-registry%2Fsh.kwant%2Fkwant?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:2cab594cbc04658b…, first seen 2026-10-17, included at leaf 4482 of 75,754. Version history · verify what your client received.

Tools (16)

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

As of 2026-10-26 22:08 UTC, the Kwant MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Kwant MCP server provide?

Kwant MCP server advertises 16 tools, including backtest, build_monthly_universe, compare_tickers, compute_correlation_matrix, compute_indicator.

How do I install Kwant MCP server?

Point your MCP client at this streamable-http endpoint: https://kwant.sh/mcp

Is the Kwant MCP server safe to connect to an AI agent?

Glimind scanned all 16 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 Kwant 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