mcp-registry/io.github.lazymac2x/crypto-signal · v1.0.0
Also listed as glama/lazymac2x/crypto-signal-api-mcp-server
As of 2026-10-20 06:17 UTC, the Lazymac2x Crypto Signal MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Cloudflare Workers MCP server: crypto-signal
Claude Code
claude mcp add --transport http lazymac2x-crypto-signal-mcp-server https://api.lazy-mac.com/crypto-signal/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"lazymac2x-crypto-signal-mcp-server": {
"type": "http",
"url": "https://api.lazy-mac.com/crypto-signal/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fcrypto-signal/fixes
{
"name": "get_crypto_indicators",
"description": "Get detailed technical indicators (RSI, MACD, EMA, Bollinger Bands, etc.) for a crypto pair",
"inputSchema": {
"type": "object",
"required": [
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"default": "BTCUSDT",
"description": "Trading pair (e.g. BTCUSDT)"
},
"interval": {
"type": "string",
"default": "1h",
"description": "Candle interval"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_crypto_signal",
"description": "Get a buy/sell/hold trading signal for a cryptocurrency pair with technical analysis",
"inputSchema": {
"type": "object",
"required": [
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"default": "BTCUSDT",
"description": "Trading pair (e.g. BTCUSDT, ETHUSDT)"
},
"interval": {
"type": "string",
"default": "1h",
"description": "Candle interval (1m,5m,15m,1h,4h,1d)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lazymac2x/crypto-signal"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/crypto-signal"}) over MCP.
get_crypto_signal ~110 tokensget_crypto_indicators ~105 tokensscreen_crypto_market ~93 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcrypto-signal?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcrypto-signal?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fcrypto-signal.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fcrypto-signal.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fcrypto-signal?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3bef2d9a8d1a1392…, first seen 2026-10-17, included at leaf 14176 of 31,206. Version history · verify what your client received.
Compare: most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 06:17 UTC, the Lazymac2x Crypto Signal MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Lazymac2x Crypto Signal MCP server advertises 3 tools, including get_crypto_indicators, get_crypto_signal, screen_crypto_market.
Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/crypto-signal/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.