Crypto-Signal

CryptoSignal is a Python command-line crypto technical analysis tool/bot that automates indicator calculations (e.g., RSI, MACD, SMA/EMA, Ichimoku, etc.) for many coins and provides alerting via channels like email, SMS (Twilio), Slack, Telegram, and Discord. It is configured via a local config.yml and typically run via Docker.

Evaluated Mar 29, 2026 (0d ago)
Homepage ↗ Repo ↗ Ai Ml ai-ml algorithmic-trading technical-analysis alerts docker python crypto
⚙ Agent Friendliness
25
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
45
Error Messages
0
Auth Simplicity
40
Rate Limits
10

🔒 Security

TLS Enforcement
70
Auth Strength
35
Scope Granularity
10
Dep. Hygiene
45
Secret Handling
35

Security aspects are not well evidenced in the provided README. The tool integrates with multiple exchanges and alert providers; credentials are likely stored in config.yml, but the README does not state how secrets are handled (e.g., env vars vs files, logging redaction). TLS is likely used for network calls but not explicitly stated. Scope granularity and auth mechanisms are not documented.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
35
Error Recovery
20
AF Security Reliability

Best When

You want a self-hosted TA/alerting CLI tool that you can configure and extend, and you are comfortable validating indicator/strategy correctness against your own expectations.

Avoid When

You need a documented, standardized API surface (REST/OpenAPI/SDKs) for agent-driven integration, or you require strong, explicit security guarantees and operational reliability documentation from the package itself.

Use Cases

  • Automated technical analysis and indicator computation for crypto markets
  • Generating alerts when indicators meet configured conditions
  • Experimenting with trading strategies or ML models using TA features
  • Running self-hosted/locally configured crypto monitoring and alerting

Not For

  • Production trading execution without thorough validation and risk controls
  • Compliance-sensitive environments that require explicit guarantees around data handling and operational SLAs (not evidenced in provided docs)
  • Use as a turnkey financial decision system (project includes liability disclaimers)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: API keys/credentials for exchanges and alert providers likely via config.yml (not explicitly detailed in provided README)
OAuth: No Scopes: No

README does not describe authentication mechanisms or scopes; it only mentions configuring config.yml and running via Docker. Security posture cannot be verified from provided content.

Pricing

Free tier: No
Requires CC: No

No pricing information in provided README; appears to be self-hosted open source (MIT license stated in repository metadata).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No clearly documented programmatic API (REST/OpenAPI/MCP/SDK); integration is primarily via running a container and managing config.yml.
  • README indicates 'documentation is often lagging' and 'Beta' state, which can lead to undocumented config fields/behaviors.
  • Operational details such as rate limits, retries, and error-handling semantics are not described in the provided content.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Crypto-Signal.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-29.

5347
Packages Evaluated
21056
Need Evaluation
586
Need Re-evaluation
Community Powered