Add Hive Intelligence to registry#27
Open
rishabhng wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi ravitemer,
This adds Hive Intelligence as a structured registry entry with both supported ways a client may connect:
NPXfor local stdio setup through the publishedhive-intelligencenpm package.Remote HTTPfor the hosted MCP endpoint athttps://mcp.hiveintelligence.xyz/mcp.I matched this registry's YAML format and parameter model so consumers can replace one
HIVE_API_KEYplaceholder in either configuration. The entry focuses on the parts that are useful for MCP client builders: crypto market data, DeFi analytics, wallet intelligence, token risk, DEX flows, NFTs, infrastructure, and prediction markets.Validation run locally:
npm run validate npm testBoth passed.