io.github.Jegoba90/cryptocapi
NPM · @CRYPTOCAPI/MCP
Análisis de mercado cripto con sello verificable: cada motor firma su análisis con SHA-256.
Available components
Last scanned (19 hours ago)
Scores higher than 95% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Jegoba90/cryptocapi-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 819 tokens (~204/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 30 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 29 Oct 26 −11
- Stability: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.0.1 → 1.0.2 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.0 → 1.0.1 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@cryptocapi/mcp@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Jegoba90/cryptocapi-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Jegoba90/cryptocapi-mcp/.github/workflows/release.yml@refs/tags/v1.0.2 |
| Rekor log index | 3567392713 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:86babd8675928d71f11715f9aeda4627cb0b04774982e659278c333d9a75a4421f5d643af45952245f924676f1355d08e44e3a47acd1c7f913d3aaafb |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batch_signals Señales de Quant Plus en lote ~167
Señales de Quant Plus para varios activos en una sola llamada. Requiere el pase Quant Plus, con una excepción: con la key pública de demostración funciona para bitcoin y ethereum, igual que get_insight. Ojo con el formato: acá van identificadores de moneda ("bitcoin"), no pares de trading, al revés que en get_signal. Solo un universo curado tiene señal, bastante más chico que el conjunto de activos que CryptoCapi sigue: un activo fuera de él vuelve con `available: false`, y eso es la respuesta correcta, no un error.
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | yes | Identificadores de moneda, de 1 a 50: ["bitcoin", "ethereum"]. El tope de 50 es del pedido, no de las señales disponibles. |
No output schema declared.
No examples provided.
get_insight Análisis de un activo ~407
Análisis de un activo con el motor determinista de CryptoCapi. La vista "pulse" no exige pase con una key del plan free. La vista "alpha" trae el análisis profundo con el audit_trail y su protocol_hash, que es el sello del cálculo, y requiere el pase Radar Alpha (o Quant Plus si se pide engine="quant_plus"). Con la key pública de demostración, que es la que se usa si no se configura otra, solo responden bitcoin y ethereum, en cualquier vista, y la respuesta es siempre la alpha: otra moneda da 403 aunque se pida "pulse". Al leer la respuesta: `z_score` mide el MOVIMIENTO del último día cerrado (UTC), no el del día en curso, contra los movimientos pasados, y la posición en Bandas de Bollinger mide el NIVEL de precio contra su rango. Son ejes distintos: precio en el tercio superior con z_score negativo no es una contradicción, es un nivel alto después de un día que cerró con una caída fuerte. No las mezcles en una sola frase. Las stablecoins se leen por la distancia de su último cierre al dólar, no por el z_score. Si la moneda todavía no tiene análisis, la respuesta es `{"status":"success","data":null}`: no es un error ni un fallo de la consulta, es que ningún motor calculó nada para ese activo. Decilo así, «no hay análisis disponible», y no completes el hueco por tu cuenta.
| Name | Type | Req | Description |
|---|---|---|---|
| coin_id | string | yes | Identificador de la moneda, en minúsculas: "bitcoin", "ethereum", "solana". |
| engine | string | – | Motor que firma el análisis. Por defecto "radar". |
| view | string | – | "pulse" no exige pase con una key free; "alpha" trae el sello y requiere pase. Con la key de demostración la respuesta es siempre alpha. Por defecto "pulse". |
No output schema declared.
No examples provided.
get_signal Señal de Quant Pro ~96
Señal cuantitativa para un par de trading. Requiere el pase Quant Pro: ningún otro motor lo habilita. Ojo con el formato, que no es el mismo que en las otras herramientas: acá va el par ("BTCUSDT"), no el identificador de moneda ("bitcoin").
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Par de trading, por ejemplo "BTCUSDT" o "ETHUSDT". No "bitcoin". |
No output schema declared.
No examples provided.
scan_market Ranking de Market Scan ~149
Recorre el mercado y devuelve los activos mejor rankeados según una estrategia. Requiere el pase Market Scan, que se vende aparte de Quant Plus aunque el ranking se arme sobre sus señales. El ranking cubre el universo curado de Quant Plus, bastante más chico que el conjunto de activos que CryptoCapi sigue, así que pedir 50 puede devolver bastante menos. Eso no es un fallo.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Cuántos activos devolver, de 1 a 50. Por defecto 10. Es un techo del pedido: si el universo rankeado es menor, vuelven menos. |
| strategy | string | – | Perfil del ranking. Por defecto "balanced". |
No output schema declared.
No examples provided.
How do I install the io.github.Jegoba90/cryptocapi MCP server?
io.github.Jegoba90/cryptocapi runs locally as an npm package, launched with npx -y @cryptocapi/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @cryptocapi/mcp
claude mcp add jegoba90-cryptocapi -- npx -y @cryptocapi/mcp
What is the io.github.Jegoba90/cryptocapi MCP server?
io.github.Jegoba90/cryptocapi is an MCP server listed in the public MCP registry as io.github.Jegoba90/cryptocapi. Análisis de mercado cripto con sello verificable: cada motor firma su análisis con SHA-256. This page covers its npm package (@cryptocapi/mcp).
Is the io.github.Jegoba90/cryptocapi MCP server safe to use?
io.github.Jegoba90/cryptocapi scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Jegoba90/cryptocapi MCP server expose?
io.github.Jegoba90/cryptocapi exposes 4 tools: get_insight, get_signal, batch_signals, scan_market. Their descriptions and schemas cost roughly 819 tokens of context every time the server is loaded.
Is the io.github.Jegoba90/cryptocapi MCP server still maintained?
io.github.Jegoba90/cryptocapi is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Jegoba90/cryptocapi MCP server under?
io.github.Jegoba90/cryptocapi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.