Tickory MCP

io.github.tickoryPublished by GitHub account tickoryv0.3.0Updated Oct 24, 2026

Tickory MCP server for Binance scans, alert events, and explainability.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local MCP server that gives an assistant access to Tickory's Binance scans, alert events and explainability data.

What you can do
Provides access to Binance market scans produced by Tickory, so an assistant can look up scan results rather than fetching market data itself. Surfaces alert events, letting an assistant review what alerts were raised. Offers explainability information behind scans and alerts, so an assistant can help interpret why a result or alert appeared. No individual tools are listed in the supplied material, so exact operations are not documented here.
When to use it
Useful when you already work with Tickory's Binance scanning and alerting and want an assistant to review scan results, alert events or the reasoning behind them in conversation. Not needed if you only want general Binance market data or trading actions.
Requirements
Runs as a local process on the user's machine, installed from the npm package @tickory/mcp over stdio, so a Node.js runtime is needed. The manifest declares no authentication, environment variables or headers; desktop use only, with no web-executable version.
Before you install
The supplied material does not describe credentials, write actions or third-party data flows, so review the package before installing. It concerns Binance market scanning and alerts, which is financial information; treat scan and alert output as informational rather than as trading advice, and check whether it can change any Tickory configuration.

Installation

In SourceWeft

  1. Open Tickory MCP 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.

Tools

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

Version history

1
  1. v0.3.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.