Universal AI Agent Discovery - search 59,000+ agents across MCP, NANDA, A2A, OpenRouter
Hashnet MCP server exists for a simple reason — assistants are far more useful when they can act on Hashnet directly instead of describing what you should do. Universal AI Agent Discovery - search 59,000+ agents across MCP, NANDA, A2A, OpenRouter.
Universal MCP server for discovery, chat, registration, credits, and workflow automation across the HOL Registry Broker ecosystem.
Once Hashnet is connected, these are the calls the assistant has available:
Discovery — hol.stats, hol.capabilities, hol.search, hol.vectorSearch, hol.resolveUaidChat — hol.chat.readiness, hol.chat.createSession, hol.chat.sendMessage, hol.chat.retry, hol.chat.history, hol.chat.resume, hol.chat.endRegistration — hol.getRegistrationQuote, hol.registerAgent, hol.waitForRegistrationCompletionWorkflows — workflow.discovery, workflow.delegate, workflow.registrationdata — metaSurface — LinkDocumentation — hol.org/mcpCodeSandbox — Open examples in browserTransport — Endpoint(s)stdio — process stdin/stdoutVariable — RequiredREGISTRY_BROKER_API_URL — noYou will need 6 environment variables: REGISTRY_BROKER_API_URL, REGISTRY_BROKER_API_KEY, MCP_SERVER_BEARER_TOKEN, LEDGER_ACCOUNT_ID, HEDERA_ACCOUNT_ID, HEDERA_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @hol-org/hashnet-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hashnet's toolset — Discovery, Chat, Registration and 11 more — is a fair guide to whether it matches your workflow. It is maintained by hashgraph-online; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Discovery | hol.stats, hol.capabilities, hol.search, hol.vectorSearch, hol.resolveUaid |
| Chat | hol.chat.readiness, hol.chat.createSession, hol.chat.sendMessage, hol.chat.retry, hol.chat.history, hol.chat.resume, hol.chat.end |
| Registration | hol.getRegistrationQuote, hol.registerAgent, hol.waitForRegistrationCompletion |
| Workflows | workflow.discovery, workflow.delegate, workflow.registration |
| data | meta |
| Surface | Link |
| Documentation | [hol.org/mcp](https://hol.org/mcp) |
| CodeSandbox | [Open examples in browser](https://codesandbox.io/p/sandbox/github/hashgraph-online/hashnet-mcp-js/tree/master) |
| Transport | Endpoint(s) |
| stdio | process stdin/stdout |
| Variable | Required |
| REGISTRY_BROKER_API_URL | no |
| REGISTRY_BROKER_API_KEY | no |
| BROKER_REQUEST_TIMEOUT_MS | no |
{
"mcpServers": {
"hashnet": {
"command": "npx",
"args": ["-y", "@hol-org/hashnet-mcp"],
"env": {
"REGISTRY_BROKER_API_URL": "your-value",
"REGISTRY_BROKER_API_KEY": "your-value",
"MCP_SERVER_BEARER_TOKEN": "your-value",
"LEDGER_ACCOUNT_ID": "your-value",
"HEDERA_ACCOUNT_ID": "your-value",
"HEDERA_PRIVATE_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| REGISTRY_BROKER_API_URL | Endpoint or connection string the server talks to. | Yes |
| REGISTRY_BROKER_API_KEY | Credential the server authenticates with. | Yes |
| MCP_SERVER_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| LEDGER_ACCOUNT_ID | Configuration value read at startup. | Optional |
| HEDERA_ACCOUNT_ID | Configuration value read at startup. | Optional |
| HEDERA_PRIVATE_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.