hive-intelligence

MCPcommunity
v1.4.0xyz.hiveintelligenceUnknownUpdated 2d agonpmGitHub

Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2d agoLast update
Reads these credentials
  • COINGECKO_PRO_API_KEYAPI keyoptional

    CoinGecko Pro API key

  • ALCHEMY_API_KEYAPI keyoptional

    Alchemy API key (EVM wallet, token, NFT, transfer, simulation, gas, and RPC data)

  • CODEX_API_KEYAPI keyoptional

    Codex GraphQL API key

  • GOPLUS_APP_KEYAPI keyoptional

    GoPlus application key

  • GOPLUS_APP_SECRETAPI keyoptional

    GoPlus application secret

  • HELIUS_API_KEYAPI keyoptional

    Helius API key (Solana RPC, Digital Asset Standard (DAS), priority fees)

  • MORALIS_API_KEYAPI keyoptional

    Moralis API key (EVM wallet, token, NFT analytics)

  • TENDERLY_API_KEYAPI keyoptional

    Tenderly API key (EVM simulation, tracing, gas estimation)

  • TENDERLY_NODE_ACCESS_KEYAPI keyoptional

    Tenderly Node access key (EVM RPC and historical state queries)

  • TENDERLY_GATEWAY_ACCESS_KEYAPI keyoptional

    Legacy alias for the Tenderly Node access key

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
Authorxyz.hiveintelligence
LicenseUnknown
Version1.4.0
Sourcenpm+mcp-registry
npmhive-intelligence
GitHubhive-intel/hive-sdk
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
—Static analysis · clean+0/20
→ Not yet scanned — package must be on npm
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

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

Tools

Not probed yet

Forge has not completed a tools/list handshake against this endpoint, so it holds no observation of what the server exposes. Nothing here says it exposes nothing.

About

Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package has not been scanned yet, so no dependency tree has been resolved.