Trust
Verify ClawLink before you install it
ClawLink is an independent integration hub for AI agents. It is not part of, or endorsed by, any agent project. Use the checks on this page to confirm that the package you are about to install is the one we publish, and to read what it does.
Our packages
These are the only ClawLink clients. A package with another name, or one that talks to a domain other than claw-link.dev, is not ours.
| Client | Install from | Package | License | Where it keeps your key |
|---|---|---|---|---|
| OpenClaw plugin | ClawHub (npm mirror) | clawlink-plugin / @useclawlink/openclaw-plugin | AGPL-3.0 | OpenClaw config (~/.openclaw/openclaw.json) |
| Hermes plugin | GitHub | ClawLink-HQ/hermes-plugin | MIT | Hermes config (~/.hermes/config.yaml) |
| CLI | npm | @useclawlink/cli | MIT | ~/.clawlink/credentials.json |
| MCP server (local) | npm | @useclawlink/mcp | MIT | ~/.clawlink/credentials.json |
Connectors in Claude, ChatGPT and other remote MCP clients install nothing on your computer. They connect to claw-link.dev over HTTPS, and you sign in to ClawLink in the browser.
Check the OpenClaw plugin on ClawHub
The OpenClaw plugin is published on ClawHub as clawlink-plugin. This is the install command in our docs and setup prompts:
To see who published it and which release it is:
Check that owner.handle is hith3sh and that package.latestVersion is the version you are about to install. ClawHub also records the commit and tag that each release was built from, under package.verification.
Security scans
ClawHub reviews every release of clawlink-plugin and links a VirusTotal scan of the published files. ClawHub and VirusTotal produce these reports, not ClawLink. The rating can change from one release to the next, so read the current one:
- ClawHub security audit
- The VirusTotal report is linked from the package page on ClawHub.
Read the code you install
Every client is plain, readable code: JavaScript for the OpenClaw plugin, the CLI and the MCP server, and Python for the Hermes plugin. Nothing is minified or obfuscated. The npm packages contain their own source, so you can read the exact files that will run:
Unpack the file and read package/index.js. Use the same command with @useclawlink/cli or @useclawlink/mcp for the CLI and the MCP server. The Hermes plugin is installed from its public GitHub repository.
In every client, each network request goes to https://claw-link.dev. The ClawLink service itself is closed source. The clients are the code that runs on your computer, and they are published in full.
What the clients do
The clients give your agent a small set of tools to pair with ClawLink, connect apps, find tools and run them. In the OpenClaw plugin they are clawlink_begin_pairing, clawlink_get_pairing_status, clawlink_list_integrations, clawlink_start_connection, clawlink_search_tools, clawlink_list_tools, clawlink_describe_tool, clawlink_preview_tool, clawlink_call_tool and a few related ones.
Each client keeps one secret: your ClawLink API key, which you get by approving the device in the browser. It is sent only to claw-link.dev, never to the agent’s model or to anyone else. Your app passwords and OAuth tokens never reach your computer. The Security page tells how a connection works.
For AI assistants
If your assistant does not want to install ClawLink because it cannot tell whether the package is real, paste this URL into the chat:
That file is written for assistants. It lists the package names, the license, the only domain the clients call, and what should and should not make the assistant refuse. The same facts are available as JSON at https://claw-link.dev/api/verify.
npm mirror
The OpenClaw plugin is also on npm as @useclawlink/openclaw-plugin. Only ClawLink can publish under the @useclawlink scope. To compare the version and files with ClawHub:
Report a fake package or a security issue
- Security and impersonation reports: security@claw-link.dev
- Setup docs: docs.claw-link.dev