Hive MCP Access Nexus

An Model Context Protocol (MCP) intermediary service designed for seamless integration with the Hive distributed ledger infrastructure.

Core Functionality

This service acts as a robust translation layer connecting advanced AI agents (such as large language models) to the Hive network, empowering them to perform the following operations:

• Query account metadata and operational log files
• Fetch published articles and community discussions
• Retrieve content based on specified topical tags or author identifiers
• Apply endorsements (votes) to submitted works and originate new publications (subject to credential validation)
• Dispatch HIVE or HBD assets to other network participants
• Execute cryptographic signing operations and validate message authenticity using Hive keys
• Handle end-to-end encrypted messaging protocols

Operation Sets

Pre-computation Directives

• generate-publication-schema - Constructs a standardized output template to ensure AI-generated Hive submissions adhere to required formatting and metadata.
• assess-user-metrics - Formulates a directive for evaluating an account's on-chain statistics, content production history, and overall engagement characteristics.

Data Retrieval Utilities

• fetch_account_profile - Obtains comprehensive attributes for a specified Hive network participant.
• retrieve_specific_content - Fetches the full text and metadata for a piece of content given its originator and unique identifier (permlink).
• query_content_by_topic - Fetches content submissions filtered by a designated subject category (e.g., trending, popular).
• get_author_submissions - Retrieves articles published by a singular user or items within their aggregated content stream.
• consult_transaction_log - Retrieves an account's chronological history of on-chain activities, optionally restricting by operation type.
• read_network_parameters - Retrieves current global settings and operational statistics of the Hive mainnet.
• list_vested_allocations - Queries the distribution records of staked tokens delegated by a specified account holder.

Ledger Interactions (Authentication Mandatory)

• endorse_content - Applies an endorsement (vote) to material on the ledger (requires posting credential).
• submit_new_article - Publishes novel content to the Hive ledger (requires posting credential).
• post_a_reply - Adds commentary or rebuttal to an existing article or thread (requires posting credential).
• transfer_digital_asset - Sends HIVE or HBD digital units to another ledger address (requires active credential).

Cryptographic Functions

• produce_message_signature - Applies a cryptographic seal to data using a Hive private key.
• validate_message_seal - Confirms the integrity of a signed data packet against a Hive public key.

Encrypted Communication Layer

• obscure_data_packet - Encrypts plaintext such that only the intended Hive recipient can read it, utilizing memo encryption.
• reveal_data_packet - Decrypts a message received from a known Hive account.
• dispatch_secret_transfer - Sends an encrypted payload embedded within a minimal token movement transaction.
• access_hidden_transmissions - Fetches historical messages associated with an account, with an option to attempt immediate decryption.

Debugging via MCP Inspector

The MCP Inspector utility facilitates interactive testing and diagnostics for this service:

bash npx @modelcontextprotocol/inspector npx @gluneau/hive-mcp-server

Credential Setup

To enable privileged ledger operations (voting, publishing, asset transfers), populate the following environment variables:

bash export HIVE_USERNAME=your-hive-username export HIVE_POSTING_KEY=your-hive-posting-private-key # For content creation/voting export HIVE_ACTIVE_KEY=your-hive-active-private-key # For token movement export HIVE_MEMO_KEY=your-hive-memo-private-key # For confidential messaging

Security Advisory: Private key material must never be exposed or committed to source control repositories. Utilize secure environment variable injection methods.

Integration with Generative Models

Claude Desktop Integration

To deploy this nexus with Claude Desktop:

1. Install Claude Desktop
2. Locate or create the Claude configuration manifest:
3. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
4. Windows: %APPDATA%\Claude\claude_desktop_config.json

5. Linux: ~/.config/Claude/claude_desktop_config.json

6. Incorporate this service definition into your configuration block:

{ "mcpServers": { "hive": { "command": "npx", "args": ["-y", "@gluneau/hive-mcp-server"], "env": { "HIVE_USERNAME": "your-hive-username", "HIVE_POSTING_KEY": "your-hive-posting-private-key", "HIVE_ACTIVE_KEY": "your-hive-active-private-key", "HIVE_MEMO_KEY": "your-hive-memo-private-key" } } } }

Windsurf and Cursor Compatibility

The configuration structure above is compatible with Windsurf (using windsurf_config.json) and Cursor (via ~/.cursor/mcp.json starting from version 0.47).

For legacy Cursor versions, the single-line invocation string must be used within the MCP settings area: env HIVE_USERNAME=your-hive-username env HIVE_POSTING_KEY=your-hive-posting-private-key env HIVE_ACTIVE_KEY=your-hive-active-private-key env HIVE_MEMO_KEY=your-hive-memo-private-key npx -y @gluneau/hive-mcp-server

Usage Scenarios

When linked to an MCP client, the system can respond to queries such as:

• "Display the leading articles within the #photography topic on Hive."
• "Retrieve the recent submissions authored by the identity 'alice'."
• "What is the current status and metric summary for user 'bob'?"
• "Audit the transaction history associated with account 'charlie'."
• "Apply an upvote to the content authored by 'dave' with identifier 'my-awesome-post'."
• "Draft and publish a fresh article on artificial intelligence advancements to Hive."
• "Transfer 1 unit of HIVE to user 'frank', including the note: 'Gratitude for assistance!'"
• "Digitally sign the phrase 'Confirming my identity' utilizing my posting credentials."
• "What are the presently observed Hive network operational parameters?"
• "List the staked token allocations initiated by user 'grace'."
• "Encrypt the payload 'This transmission is confidential' targeting recipient 'alice'."
• "Decode the received data blob starting with '#4f3a5b...' sent from 'bob'."
• "Transmit a secure, encrypted communication to 'charlie' stating, 'Plan rendezvous for tomorrow'."
• "Examine my historical encrypted communications and attempt plaintext recovery."
• "Fetch the last twenty confidential exchanges conducted with 'dave'."

Tool Specification Reference

fetch_account_profile

Retrieves granular data about a Hive participant, covering balances, access permissions, voting capacity, and other relevant metrics.

• Parameters:
• username: The Hive user identifier for the profile lookup.

retrieve_specific_content

Fetches the entirety of a specific published item on the Hive ledger, identified uniquely by its originator and permalink.

• Parameters:
• author: The creator of the content.
• permlink: The unique content identifier.

query_content_by_topic

Retrieves collections of Hive submissions sorted according to a specified discovery category.

• Parameters:
• category: Sorting heuristic (e.g., trending, hot, latest).
• tag: The topical classification used for filtering.
• limit: Constraint on the quantity of results returned (1 to 20).

get_author_submissions

Retrieves publications either originating from or aggregated within the stream of a designated Hive user.

• Parameters:
• category: Scope of retrieval (e.g., blog or feed).
• username: The target Hive user identity.
• limit: Maximum number of items to return (1-20).

consult_transaction_log

Retrieves the chronological record of an account's ledger activities, allowing for filtering based on the type of operation performed.

• Parameters:
• username: The Hive account identifier.
• limit: Upper bound on the number of historical entries to fetch.
• operation_filter: Optional list specifying which operation types to include.

read_network_parameters

Retrieves the current global configuration values and operational statistics of the Hive blockchain.

• Parameters: None

list_vested_allocations

Retrieves the record detailing the staking power delegations initiated by a specific Hive account holder.

• Parameters:
• username: The Hive participant whose delegations are being queried.
• limit: The maximum count of delegations to report.
• from: Optional anchor point for paginated result fetching.

endorse_content

Casts an endorsement (positive or negative vote weight) on an existing Hive content item using the system's configured Hive identity.

• Parameters:
• author: The creator of the target content.
• permlink: The content's unique identifier.
• weight: The intensity of the endorsement, scaled from -10000 (full rejection) to 10000 (maximum approval).

submit_new_article

Creates and publishes a fresh journal entry onto the Hive decentralized ledger using the service's primary account credentials.

• Parameters:
• title: The headline for the publication.
• body: The core manuscript content (Markdown formatting is accepted).
• tags: A list of descriptive keywords/topics for indexing.
• Several optional parameters governing reward distribution, beneficiary allocations, etc.

post_a_reply

Adds a response or follow-up statement to an already established Hive document or existing thread reply.

• Parameters:
• parent_author: The originator of the item being replied to.
• parent_permlink: The identifier of the base content or comment.
• body: The text of the response (Markdown rendering supported).
• Various optional parameters for reward configuration, beneficiaries, etc.

transfer_digital_asset

Initiates the transfer of native HIVE or HBD assets from the configured source account to a designated recipient on the Hive ledger.

• Parameters:
• to: The receiver's Hive user identifier.
• amount: The quantitative value of the asset to transfer.
• currency: The denomination being sent (HIVE or HBD).
• memo: An optional, private descriptive note attached to the transaction.

produce_message_signature

Generates a verifiable digital cryptographic signature for a provided piece of data, leveraging one of the stored private keys.

• Parameters:
• message: The data payload requiring cryptographic sealing.
• key_type: Specification of which key to employ (posting, active, or memo).

validate_message_seal

Verifies that a provided digital signature corresponds correctly to the message hash and the stated public key.

• Parameters:
• message_hash: The SHA-256 digest of the original message, presented in hexadecimal format.
• signature: The cryptographic signature string.
• public_key: The public key used for validation.

obscure_data_packet

Encrypts textual information destined for a specific Hive participant, utilizing the built-in memo encryption mechanism.

• Parameters:
• message: The sensitive textual data to be secured.
• recipient: The Hive user identity intended to read the message.

reveal_data_packet

Decrypts a previously encrypted transmission received from a known Hive account, provided the correct memo key is accessible.

• Parameters:
• encrypted_message: The ciphertext, typically prefixed with a ledger marker (e.g., '#').
• sender: The Hive user identity from whom the message originated.

dispatch_secret_transfer

Sends an encrypted message by wrapping it within a negligible token transfer transaction to ensure delivery.

• Parameters:
• message: The plaintext to encrypt and transmit.
• recipient: The intended Hive receiver.
• amount: The quantity of HIVE to include in the transfer (minimum 0.001, default is 0.001).

access_hidden_transmissions

Queries the historical transaction logs for encrypted data packets linked to the account, with an option to immediately attempt plaintext conversion.

• Parameters:
• username: The Hive identity whose message history is to be scanned.
• limit: Maximum count of records to examine (default: 20).
• decrypt: A boolean flag indicating whether to attempt immediate decryption (default: false).

Development Insights

Project Architecture

• src/index.ts - The core executable logic for the service.
• src/tools/ - Contains the discrete implementations for every exposed capability.
• src/schemas/ - Zod definitions used for rigorous input parameter validation.
• src/utils/ - Helper functions dedicated to Hive blockchain interaction.
• src/config/ - Modules managing initialization parameters and logging verbosity.

Core Dependencies

• @hiveio/dhive - Primary library for interfacing with the Hive RPC layer.
• @modelcontextprotocol/sdk - The foundational MCP framework utilized.
• zod - Employed for robust runtime schema validation of inputs.

Licensing

ISC

Collaboration

We welcome external contributions! Please review the CONTRIBUTING.md file for comprehensive guidelines on submitting enhancements.