@cryptocapi/mcp

Name: @cryptocapi/mcp
Author: Unknown

MCPattested

v0.2.3UnknownMITUpdated 1d agonpm GitHub

Servidor MCP de CryptoCapi: analisis cripto con sello verificable, expuesto como tools nativas para agentes.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

278Downloads/wk

1d agoLast update

Reads these credentials

CRYPTOCAPI_API_KEYAPI keyoptional
API key de CryptoCapi. Opcional: sin ella se usa la key pública de demostración demo_btc_eth_public, que sirve análisis de bitcoin y ethereum sin registro. Una key propia abre el resto del universo y…

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

AuthorUnknown

LicenseMIT

Version0.2.3

Sourcenpm+mcp-registry

npm@cryptocapi/mcp

GitHubJegoba90/cryptocapi-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · c3a6a6b

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv0.2.3 · todayHow well does this scan work?

EvalsNone

IndexedSep 5, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev0.2.3 · 2h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_insightAnálisis de un activo con el motor determinista de CryptoCapi. La vista "pulse"

Análisis de un activo con el motor determinista de CryptoCapi. La vista "pulse"

No input schema was published for this tool.

get_signalSeñal cuantitativa para un par de trading. Requiere el pase Quant Pro: ningún otro

Señal cuantitativa para un par de trading. Requiere el pase Quant Pro: ningún otro

No input schema was published for this tool.

batch_signalsSeñales de Quant Plus para varios activos en una sola llamada. Requiere el pase

Señales de Quant Plus para varios activos en una sola llamada. Requiere el pase

No input schema was published for this tool.

scan_marketRecorre el mercado y devuelve los activos mejor rankeados según una estrategia.

Recorre el mercado y devuelve los activos mejor rankeados según una estrategia.

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Servidor MCP de CryptoCapi: analisis cripto con sello verificable, expuesto como tools nativas para agentes.

Keywords

mcpmodel-context-protocolcryptocapicryptomarket-analysis

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-05 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.7
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

@cryptocapi/mcp

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in crypto & web3