Crypto Signals MCP

io.github.agenthustlerPublished by GitHub account agenthustlerv1.0.2Updated Oct 24, 2026

Real-time crypto volume anomaly detection across 50+ tokens with pump signals.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server that detects real-time crypto volume anomalies across 50+ tokens and surfaces pump signals to an assistant.

What you can do
  • Detect real-time volume anomalies across more than 50 crypto tokens.
  • Surface pump signals derived from those volume anomalies.
  • No tool list is published, so the exact operations an assistant can call are not documented.
When to use it
Worth considering when you want an assistant to watch crypto market volume for unusual activity or pump-style signals while you work locally. Not useful if you need documented tools, historical analysis, or trading execution.
Requirements
Runs as a local process over stdio, installed from the PyPI package crypto-signals-mcp, so a Python environment is needed. No authentication, environment variables or headers are declared. Network access is implied by real-time market data but not stated.
Before you install
Signals are market indicators, not investment advice, and pump signals can be noisy or manipulated. No tools, data sources, update frequency or rate limits are documented, so verify behavior before relying on it. It is desktop-only and cannot be run in a web client.

Installation

In SourceWeft

  1. Open Crypto Signals 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.

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. v1.0.2LatestSep 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.

Other Signals integrations