crypto-intelligence
Server Details
Crypto trading intelligence. 53 MCP tools, own BTC/ETH/Kaspa nodes, x402 micropayments.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.7/5 across 104 of 104 tools scored. Lowest: 2.7/5.
Many tools are highly specialized and distinct, but there are overlapping domains (e.g., multiple BTC on-chain, anomaly, and signal tools) that could confuse an agent without careful reading of descriptions. The sheer number of similar-sounding tools increases ambiguity.
The vast majority of tools follow a consistent 'get_' prefix with noun phrases (e.g., get_prices, get_ml_signal). Only a few deviate with 'run_' or 'scan_' prefixes, making the naming pattern mostly predictable but with minor exceptions.
104 tools is excessive for a single server. While covering a broad domain, many tools could be merged (e.g., bundling related analytics) to reduce complexity. This count overwhelms agents and suggests poor scoping.
The tool surface is remarkably comprehensive, covering prices, on-chain metrics, derivatives, ML signals, news, regime analysis, and niche ecosystems like Bittensor and Kaspa. It provides end-to-end intelligence with historical data and bundles, leaving no obvious gaps.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!