hashnet -js

This MCP server exposes Hashnet MCP tooling that enables discovery, registration, and chat sessions with agents and MCP servers on the Hashgraph network. It ships a comprehensive toolset under the hol.* namespace for operations like discovery (searching for registries and agents), registration (quoting, submitting registrations, and awaiting completion), and chat (creating and managing sessions, sending messages, and handling encrypted conversations). It also includes workflows for end-to-end tasks such as full registration, open chat sessions, and health/ops checks. To use it, start the server with the provided npx command and point your MCP client to the HTTP SSE stream endpoint. The available tools cover discovery, registration, chat, protocols, ops, and credits, as well as a variety of workflows to automate common registry journeys.

Prerequisites

• Node.js 18+ installed on your machine
• pnpm or npm for package management
• Internet access to install npm packages

Installation steps

1. Install dependencies and set up environment

pnpm install
# or if you prefer npm: npm install
cp .env.example .env  # then edit to add REGISTRY_BROKER_API_KEY and REGISTRY_BROKER_API_URL

2. Run the MCP server (SSE transport on port 3333)

npx @hol-org/hashnet-mcp up --transport sse --port 3333
# or from source after install: pnpm dev:sse

3. Verify the server is running

• Point your MCP client to http://localhost:3333/mcp/stream (or /mcp/sse if your client expects SSE)

Notes

• If you prefer a different transport or port, adjust the --transport and --port options accordingly.
• Ensure REGISTRY_BROKER_API_KEY is set in the environment to access HOL Registry Broker APIs.

Tips and caveats:

• You must supply a valid HOL Registry Broker API key via REGISTRY_BROKER_API_KEY and the API URL via REGISTRY_BROKER_API_URL for the tooling to function against the HOL registry.
• If MEMORY or advanced features are used, consider setting MEMORY_ENABLED and related MEMORY_ environment variables as described in the project docs.
• For production, consider running under a process manager and configuring TLS/reverse proxy for secure access to the /mcp/stream endpoint.
• The CLI supports multiple transports (stdio, sse). Use the one that matches your client integration (e.g., standard HTTP SSE for web clients, or stdio for local desktop integrations).
• When upgrading, review release notes for changes to tool namespaces and workflow payloads to maintain compatibility.