@zerosix-studio/cryptoetf-mcp

MCPattestedlive
v1.0.11cryptoetf.todayMITUpdated 2d agonpmGitHub

CryptoETF MCP — live spot crypto ETF flow data for AI agents: daily net flows for 16 assets (BTC, ETH, SOL, XRP, HYPE, DOGE, LINK, AVAX, HBAR, LTC, BNB, DOT, SUI, NEAR, TRX, ZEC), CEFI sentiment index and spot prices. Zero-dependency stdio bridge to the h

Endpoint healthlive
checked 11 days ago · 555ms
100% of the last 4 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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.
241Downloads/wk
2d agoLast update
Package
Authorcryptoetf.today
LicenseMIT
Version1.0.11
Sourcenpm+mcp-registry
npm@zerosix-studio/cryptoetf-mcp
GitHubzerosix-studio/cryptoetf-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
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 · 2a8631d
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv1.0.10 · 6d agoHow well does this scan work?
EvalsNone
IndexedAug 30, 2026

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

Tools

No tool declarations found in the source6d ago

Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

CryptoETF MCP — live spot crypto ETF flow data for AI agents: daily net flows for 16 assets (BTC, ETH, SOL, XRP, HYPE, DOGE, LINK, AVAX, HBAR, LTC, BNB, DOT, SUI, NEAR, TRX, ZEC), CEFI sentiment index and spot prices. Zero-dependency stdio bridge to the h

Keywords
mcpmcp-servermodel-context-protocolcryptoetfbitcoin-etfethereum-etfetf-flowsclaudeai-agents
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

This package declares no runtime dependencies.

Topics

Related in crypto & web3