Skip to content
MCP Server Directory logo
developer-tools

Hashnet Mcp Js

Universal MCP Server for finding + connecting to agents anywhere on the planet. https://hol.org/mcp

Reviewed overview

MCP 服务器概览

What is Hashnet MCP JS? Hashnet MCP JS is a universal MCP (Message/Model/Metadata Control Plane) server implementation for discovering and connecting to agents globally. It provides discovery, chat/session management, agent registration, credits/billing hooks, and workflow automation integrated with the HOL Registry Broker ecosystem.

How to use Hashnet MCP JS?

  • Install or run via npm/pnpm or npx: e.g. pnpm install then pnpm dev:http or use npx @hol-org/hashnet-mcp --http --host 127.0.0.1 --port 3333. The CLI binary is exposed as hashnet-mcp when installed globally or linked.
  • Launch modes: stdio (local agent runtimes), HTTP/streamable HTTP, or legacy SSE endpoints (optional). Typical quickstart: copy .env.example to .env and run pnpm dev:http.
  • Configure via environment variables (REGISTRY_BROKER_API_URL, REGISTRY_BROKER_API_KEY, MCP_TRANSPORT, MCP_HOST, MCP_PORT, MCP_SERVER_BEARER_TOKEN, ledger/crypto vars for Hedera/EVM, session/timeouts, etc.).

Key features

  • Discovery tools: hol.stats, hol.capabilities, hol.search, hol.vectorSearch, hol.resolveUaid.
  • Chat/session APIs: hol.chat.createSession, hol.chat.sendMessage, hol.chat.history, hol.chat.resume, hol.chat.end, hol.chat.retry.
  • Registration & billing: hol.getRegistrationQuote, hol.registerAgent, hol.waitForRegistrationCompletion.
  • Workflows: workflow.discovery, workflow.delegate, workflow.registration.
  • Supported transports: stdio (stdin/stdout), streamable HTTP endpoints (/mcp, /mcp/stream), legacy HTTP + SSE (optional: /mcp/sse, /mcp/messages).
  • Runtime endpoints: /healthz, /readyz, /metrics.
  • Structured tool responses and machine-readable errors (structuredContent envelopes, isError with code/category/retryable).
  • Security defaults: binds to 127.0.0.1 by default, Origin validation, bearer-token enforcement for non-local binds, session reaping, log redaction.

Common use cases

  1. Agent discovery and matchmaking across the HOL Registry Broker network.
  2. Running local agent runtimes connected via stdio for development or embedded deployments.
  3. Exposing agents over HTTP with streamable message transport for production services.
  4. Automating agent registration, onboarding, and workflow delegation across registries.
  5. Integrating agent-based capabilities with Hedera/EVM identities and paid tool access via broker API keys.

FAQ

  • How do I start the server? Use pnpm dev:http or npx @hol-org/hashnet-mcp --http; see the repo README for quickstart commands and .env configuration.

  • What transports are supported? stdio (best for local agent runtimes), streamable HTTP (/mcp, /mcp/stream), and optional legacy HTTP+SSE endpoints when enabled.

  • How is authentication handled? The server enforces bearer-token auth when binding to non-local hosts; you can also set MCP_SERVER_BEARER_TOKEN and origin allowlists.

  • How does it integrate with the Registry Broker? Configure REGISTRY_BROKER_API_URL and optional REGISTRY_BROKER_API_KEY to enable discovery, registration, and paid tools via the broker.

  • Can I use it with Hedera or EVM ledgers? Yes — environment variables support HEDERA_ACCOUNT_ID, HEDERA_PRIVATE_KEY, HEDERA_NETWORK, and EVM/Eth private key and network entries for ledger-backed operations.

  • Where are docs and examples? Repo: https://github.com/hashgraph-online/hashnet-mcp-js, package: @hol-org/hashnet-mcp on npm, and documentation at https://hol.org/mcp. CodeSandbox examples are included in the repo.