Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OpenClaw MCP Server

NPM · OPENCLAW-MCP · 2 COMPONENTS · SCANNED SEP 20

MCP server bridging Claude.ai/Desktop with self-hosted OpenClaw via OAuth 2.1.

0 this week 94 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 35 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to freema/openclaw-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 55 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 415 tokens (~59/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "openclaw_chat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the OpenClaw MCP Server server?

OpenClaw MCP Server runs locally as an npm package, launched with npx -y openclaw-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · openclaw-mcp

# add to Claude Code
claude mcp add freema-openclaw-mcp -- npx -y openclaw-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "freema-openclaw-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "openclaw-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "freema-openclaw-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "openclaw-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add freema-openclaw-mcp -- npx -y openclaw-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "freema-openclaw-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "openclaw-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add freema-openclaw-mcp --command npx --arg -y --arg openclaw-mcp
# ~/.hermes/config.yaml
mcp_servers:
  freema-openclaw-mcp:
    command: "npx"
    args: ["-y", "openclaw-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "freema-openclaw-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "openclaw-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add freema-openclaw-mcp -t stdio -c npx -a -y openclaw-mcp
// mcp.json
{
  "mcpServers": {
    "freema-openclaw-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "openclaw-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/openclaw-mcp@1.7.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo freema/openclaw-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/freema/openclaw-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2255727451
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:671a35fef1b4f96c57c0d754d0e71e5155b6510593f5f03553fc69de1011cedf814581e5d919187c047aa02265ddce9942f762bd1890da5cfafd3d2e6

Background: How many MCP packages publish verified provenance →

Dependencies 111 packages
Packages resolved 111
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~415 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
openclaw_chat ~80

Send a message to OpenClaw and get a response

NameTypeReqDescription
instancestringTarget OpenClaw instance name. Use openclaw_instances to list available instances. Defaults to the default instance.
messagestringyesThe message to send to OpenClaw
session_idstringOptional session ID for conversation context

No output schema declared.

No examples provided.

openclaw_chat_async ~108

Send a message to OpenClaw asynchronously. Returns a task_id immediately that can be polled for results. Use this for potentially long-running conversations.

NameTypeReqDescription
instancestringTarget OpenClaw instance name. Defaults to the default instance.
messagestringyesThe message to send to OpenClaw
prioritynumberTask priority (higher = processed first). Default: 0
session_idstringOptional session ID for conversation context

No output schema declared.

No examples provided.

openclaw_instances ~45

List all configured OpenClaw instances. Shows instance names, URLs, and which is the default. Use instance names in other tools to target a specific OpenClaw gateway.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

openclaw_status ~39

Get OpenClaw gateway status and health information

NameTypeReqDescription
instancestringTarget OpenClaw instance name. Defaults to the default instance.

No output schema declared.

No examples provided.

openclaw_task_cancel ~38

Cancel a pending task. Only works for tasks that haven't started yet.

NameTypeReqDescription
task_idstringyesThe task ID to cancel

No output schema declared.

No examples provided.

openclaw_task_list ~60

List all tasks. Optionally filter by status, session, or instance.

NameTypeReqDescription
instancestringFilter by instance name
session_idstringFilter by session ID
statusstringFilter by task status

No output schema declared.

No examples provided.

openclaw_task_status ~45

Check the status of an async task. Returns status, and result if completed.

NameTypeReqDescription
task_idstringyesThe task ID returned from openclaw_chat_async

No output schema declared.

No examples provided.

Common questions

What is the OpenClaw MCP Server server?

OpenClaw MCP Server is listed in the public MCP registry as io.github.freema/openclaw-mcp. MCP server bridging Claude.ai/Desktop with self-hosted OpenClaw via OAuth 2.1. This page covers its npm package (openclaw-mcp).

Is the OpenClaw MCP Server server safe to use?

OpenClaw MCP Server scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the OpenClaw MCP Server server expose?

OpenClaw MCP Server exposes 7 tools: openclaw_chat, openclaw_status, openclaw_chat_async, openclaw_task_status, openclaw_task_list, and 2 more. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Is the OpenClaw MCP Server server still maintained?

OpenClaw MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the OpenClaw MCP Server server under?

OpenClaw MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.