A
licenseA
qualityC
maintenanceKronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base.
11
72 npm
1
MIT
crypto-signals-mcp
Related Servers
Alternatives to crypto-signals-mcp
- AlicenseAqualityAmaintenanceMCP server for purchasing Kronos market intelligence via x402 USDC payments on Base, providing tools for risk, whale flows, signals, history, forecasts, and auditable decision journaling.848 npm1MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server providing 50+ crypto, market intelligence, and AI inference endpoints with x402 pay-per-request micropayments on Base.1Apache 2.0
- AlicenseAqualityCmaintenanceMarket intelligence MCP server enabling AI agents to buy crypto sentiment reads, divergence verdicts, and analyst answers via pay-per-call x402 micropayments on Base.670 npmMIT
- AlicenseAqualityFmaintenanceAn MCP server that delivers cryptocurrency sentiment analysis to AI agents.547MIT
- AlicenseAqualityBmaintenanceMCP server that aggregates x402 crypto services as tools for AI agents, providing prices, sentiment, funding rates, and technical indicators with x402 pay-per-call on Base.61,535 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing real-time crypto prices (Chainlink + Binance), Polymarket prediction market data, deep web research, and JS-rendered web scraping. All services available via x402 Solana micropayments.MIT
- AlicenseNot gradedqualityDmaintenancePay-per-call MCP server offering crypto market signals, web page extraction, and GitHub repo auditing, with automatic settlement in USDC via the x402 protocol.MIT
TDQS
A3.7/5.0
Scored across 10 tools
Disambiguation4/5
Most tools target distinct capabilities: signals, risk, history, preflight, decision creation, audit, forecast, single signal, whale alerts, and feedback. The overlap between get_crypto_signals and get_single_crypto_signal is clarified by descriptions (multi-symbol vs. single-symbol compatibility route), and get_crypto_forecast adds price-interval data. Overall, boundaries are clear enough with only minor potential confusion.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern: get_crypto_* for retrievals, audit_crypto_decision for auditing, and submit_crypto_feedback for submissions. No mixing of naming conventions like camelCase or inconsistent verb styles. The pattern is predictable across the entire set.
Tool Count5/5
With 10 tools, the count is well within the ideal 3-15 range and each tool earns its place for the crypto-signals domain. The set covers data retrieval, risk assessment, decision journaling, auditing, forecasting, and user feedback without feeling bloated or sparse.
Completeness4/5
The tool surface covers the core lifecycle: retrieving signals, risk state, history, preflight checks, creating decision journals, auditing them against outcomes, forecasts, whale alerts, and feedback. Minor gaps exist, such as no direct listing/update/delete for decision journals, but these are not critical dead ends for the primary use case of obtaining and acting on crypto intelligence.
Maintenance
ActivityMaintained
ResponsivenessNo issues