Cryptyx Mcp Server

io.github.cryptyx-aiPublished by GitHub account cryptyx-aiv0.8.0Updated Oct 24, 2026

Institutional crypto intelligence for agents. 30 tools: signals, backtests, regime, triggers.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant institutional-style crypto market intelligence: trading signals, backtests, market regime and triggers.

What you can do
  • Retrieve crypto trading signals
  • Run and review backtests
  • Check market regime assessments
  • Manage or evaluate triggers
  • All of this is exposed through roughly 30 tools, according to the provider's description.
When to use it
Useful when an assistant needs quantitative crypto market context — signals, historical backtests, regime classification or trigger conditions — rather than raw price lookups. Suited to research and analysis workflows that already rely on the Cryptyx platform.
Requirements
Runs locally over stdio, installed from the npm package @cryptyx/mcp-server (Node.js required). Needs a Cryptyx API key in CRYPTYX_API_KEY; the API base URL can be overridden with CRYPTYX_API_URL. Network access to the Cryptyx API is required. Desktop only.
Before you install
Requires a paid or account-bound API key (CRYPTYX_API_KEY) that is sent to the Cryptyx service; keep it out of shared configs. Signals, backtests and regime data are third-party market intelligence, not investment advice, and backtest results do not guarantee future performance. The manifest lists no tools, so review the actual tool set before relying on it.

Installation

In SourceWeft

  1. Open Cryptyx Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.