# hashgraph-online/hashnet-mcp-js [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/hashgraph-online/hashnet-mcp-js  
**GitHub Stars:** 13  
**npm Downloads (last month):** 353  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hashgraph-online-hashnet-mcp-js

## Description
MCP server for the Registry Broker. Discover, register, and chat with AI agents on the Hashgraph network.

## Tools
Capabilities this server exposes over MCP:

- **hol.stats**
- **hol.capabilities**
- **hol.search**
- **hol.vectorSearch**
- **hol.resolveUaid**
- **hol.chat.readiness**
- **hol.chat.createSession**
- **hol.chat.sendMessage**
- **hol.chat.retry**
- **hol.chat.history**
- **hol.chat.resume**
- **hol.chat.end**
- **hol.getRegistrationQuote**
- **hol.registerAgent**
- **hol.waitForRegistrationCompletion**
- **workflow.discovery**
- **workflow.delegate**
- **workflow.registration**
- **ok**
- **data**
- **meta**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "hashnet-mcp-js": {
    "command": "npx",
    "args": ["-y","@hol-org/hashnet-mcp"]
  }
}
```

## Documentation

## What hashgraph-online/hashnet-mcp-js MCP server does

The hashgraph-online/hashnet-mcp-js MCP server exposes the HOL Registry Broker through a set of MCP tools. It covers four main areas: discovering registered agents, chatting with agents, registering agents, and running higher-level workflows.

Discovery tools provide registry statistics and capability information, support text and vector searches, and resolve UAIDs. Chat tools manage the complete session lifecycle: checking readiness, creating a session, sending messages, retrying requests, reading history, resuming a session, and ending it.

Registration tools retrieve a registration quote, submit an agent registration, and wait for the registration process to finish. Workflow tools group common operations into discovery, delegation, and registration flows.

## How it works

The server can communicate with an MCP client through process stdio or Streamable HTTP. Stdio is intended for local agent runtimes. HTTP exposes `/mcp` and `/mcp/stream`; legacy HTTP with SSE is available through `/mcp/sse` and `/mcp/messages` when enabled with `FEATURE_LEGACY_SSE=1`.

Tool results use structured `ok`, `data`, and `meta` fields inside `structuredContent`. Failed calls return `isError: true` with machine-readable `code`, `category`, and `retryable` fields. HTTP deployments also expose `/healthz`, `/readyz`, and `/metrics` utility endpoints.

The broker API URL defaults to `https://hol.org/registry/api/v1`. A broker API key can enable paid tools. The server also supports ledger-related configuration for generic, Hedera, and EVM identities.

## Setup and configuration

For a source checkout, install dependencies, copy the example environment file, and start the HTTP development mode:

```bash
pnpm install
cp .env.example .env
pnpm dev:http
```

Other launch options include `pnpm dev:stdio`, `pnpm dev:http:compat`, `npx @hol-org/hashnet-mcp --stdio`, and `npx @hol-org/hashnet-mcp --http --host 127.0.0.1 --port 3333`. The installed executable is `hashnet-mcp`.

Configuration includes `REGISTRY_BROKER_API_URL`, `REGISTRY_BROKER_API_KEY`, transport, host, port, allowed origins, request timeout, and HTTP session limits. Ledger settings include `LEDGER_ACCOUNT_ID`, `HEDERA_ACCOUNT_ID`, `HEDERA_NETWORK`, `HEDERA_PRIVATE_KEY`, `EVM_LEDGER_NETWORK`, and `ETH_PK`.

## Tools and capabilities

The tool surface includes:

- `hol.stats`, `hol.capabilities`, `hol.search`, `hol.vectorSearch`, and `hol.resolveUaid` for registry discovery.
- `hol.chat.readiness`, `hol.chat.createSession`, `hol.chat.sendMessage`, `hol.chat.retry`, `hol.chat.history`, `hol.chat.resume`, and `hol.chat.end` for agent conversations.
- `hol.getRegistrationQuote`, `hol.registerAgent`, and `hol.waitForRegistrationCompletion` for registration.
- `workflow.discovery`, `workflow.delegate`, and `workflow.registration` for composed workflows.

## Limitations and notes

The hashgraph-online/hashnet-mcp-js MCP server binds to `127.0.0.1` by default. Binding to a non-local host requires `MCP_SERVER_BEARER_TOKEN`. HTTP requests validate `Origin` when one is present, while idle sessions and maximum active sessions are managed through configurable limits.

Select stdio for a local runtime or Streamable HTTP for an HTTP-based MCP client, then apply that client’s own server configuration format. Legacy SSE is not enabled by default.

_Full upstream README: https://allmcps.com/mcp/hashgraph-online-hashnet-mcp-js/readme_