xyz.hiveintelligence/mcp

Name: xyz.hiveintelligence/mcp
Author: xyz.hiveintelligence

MCPcommunitylive

v1.1.4xyz.hiveintelligenceUnknownUpdated 4mo agoGitHub

Crypto intelligence MCP for market data, DeFi, wallets, security, DEX, NFTs, and Solana.

Managed crypto market infrastructure for AI agents. One hosted MCP server. 369 live tools. 10 categories. 9 data providers — Alchemy, CoinGecko, DeFiLlama, Moralis, Codex, GoPlus, Helius, Tenderly, and CCXT normalized into a single agent-ready surface, so your agent gets prices, DeFi, wallets, security, and DEX flows through one API key instead of separate provider credentials. Connect · Tools ·…

Endpoint healthlive

checked 5 days ago · 2459ms

100% of the last 5 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (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 →

18GitHub stars

6Forks

4mo agoLast update

Package

Authorxyz.hiveintelligence

LicenseUnknown

Version1.1.4

Sourcemcp-registry

GitHubhive-intel/hive-sdk

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/30

→ Publisher: run `forge publish` from the repo to claim ownership

—Domain verification+0/10

→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.

✓Prompt-injection scan · clean+30/30

✓Obfuscation / exfil scan · clean+20/20

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

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface4 tools · none privileged

Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 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 packagevHEAD · 3mo 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.

search_toolsNo description published

This tool published no description. Forge does not invent one.

get_api_endpoint_schemaNo description published

This tool published no description. Forge does not invent one.

invoke_api_endpointNo description published

This tool published no description. Forge does not invent one.

researchNo description published

This tool published no description. Forge does not invent one.

0 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

Keywords

mcp

Alternatives

Comparing tool surfaces…

xyz.hiveintelligence/mcp

Tools

Tools exposed

No dependency coverage