updated 2026-10-17 20:06 UTC

OpenClaw MCP Server

Repository Website by freema

🦞 MCP server for OpenClaw - secure bridge between Claude.ai and your self-hosted OpenClaw assistant with OAuth2 authentication

MCP Servers TypeScript Listed MIT

Is OpenClaw MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.8 / 10
Provenance Attested
Signed commits 28%
Last push 28d ago
Advisories None known
Compare OpenClaw MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: OpenClaw MCP Server scores 68.1/100 (Grade B), ranked #405 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.8/10; 28% of recent commits are signed; no published advisory affects its latest release (openclaw-mcp); last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenClaw MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenClaw MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/freema/openclaw-mcp, MIT, last pushed 2026-09-19. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 5
    Packaging 10
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm openclaw-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: openclaw-mcp 1.7.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-12 OSSF Scorecard: 4.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues OpenClaw MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How OpenClaw MCP Server compares in MCP Servers

  1. #240 Obsidian MCP Server 68.1 ±0
  2. #241 Sentry MCP 68.1 ±0
  3. #242 OpenClaw MCP Server 68.1 this agent
  4. #243 Upstash MCP Server 68.1 ±0
  5. #244 Grafana MCP Server 68.0 −0.1

Bars show each HVTrust score; the tick marks OpenClaw MCP Server’s 68.1.

Where the 68.1 comes from

HVTrust dimensions vs the MCP Servers average

68.1 / 100 · 100.0% confidence

OpenClaw MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.7 / 25
3.2 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
0.6 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.3 / 20
1.0 below avg 12.3
AdoptionLog-scaled stars · package downloads
8.7 / 20
1.3 above avg 7.4

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-07
Rank Moved
Rank dropped 10 spots (#374 → #384)
2026-10-05
Rank Moved
Rank dropped 10 spots (#361 → #371)
2026-10-04
Rank Moved
Rank dropped 10 spots (#351 → #361)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for OpenClaw MCP Server View MCP Servers Report missing data
45.1
Activity sub-score · out of 100
#242
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-17 20:06 UTC · Repo last pushed 28 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
187
Forks
25
Last Push
2026-09-19
28 days ago
Commits (4 wk)
1
Downloads (7d)
284
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
=
was #405

Analysis

Activity Inputs

45.1 / 100
StarsRepository reach
13.6 / 30
FreshnessLast push recency
21.1 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
6.6 / 20

Common questions about OpenClaw MCP Server

OpenClaw MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does OpenClaw MCP Server publish package provenance?
Yes. OpenClaw MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OpenClaw MCP Server have an OpenSSF Scorecard?
OpenClaw MCP Server has an OpenSSF Scorecard score of 3.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is OpenClaw MCP Server actively maintained?
Maintained. Last push was 28 days ago.
What license does OpenClaw MCP Server use?
OpenClaw MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenClaw MCP Server's commits signed?
28% of the last 100 commits to OpenClaw MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
OpenClaw MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to OpenClaw MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain OpenClaw MCP Server?

For maintainers

HVTrust scores OpenClaw MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 28HVTrust 4Grade 3Listed 2Scorecard 1Score 1Delisted 1Provenance 1MCP 1Surface 1Surface 1
2026-10-07
Rank Moved
Rank dropped 10 spots (#374 → #384)
2026-10-05
Rank Moved
Rank dropped 10 spots (#361 → #371)
2026-10-04
Rank Moved
Rank dropped 10 spots (#351 → #361)
2026-09-27
Rank Moved
Rank rose 16 spots (#358 → #342)
2026-09-24
Rank Moved
Rank dropped 15 spots (#336 → #351)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 656 spots (#992 → #336)
2026-09-23
HVTrust Changed
HVTrust up 44.4pts (25.1 → 69.5)
2026-09-22
Newly Listed
First tracked at rank #992
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 13 spots (#321 → #334)
2026-09-19
Rank Moved
Rank rose 77 spots (#398 → #321)
2026-09-19
HVTrust Changed
HVTrust up 3.4pts (67.0 → 70.4)
2026-09-19
Activity Score Changed
Activity score up 8pts (41 → 49)
2026-09-15
Rank Moved
Rank dropped 33 spots (#356 → #389)
2026-09-12
Scorecard Added
OSSF Scorecard: 4.0/10
2026-09-12
Grade Changed
Trust grade C → B
2026-09-12
Rank Moved
Rank rose 250 spots (#598 → #348)
2026-09-12
HVTrust Changed
HVTrust up 8.4pts (60.2 → 68.6)
2026-09-11
Rank Moved
Rank dropped 15 spots (#583 → #598)
2026-09-09
Rank Moved
Rank dropped 27 spots (#552 → #579)
2026-09-08
Rank Moved
Rank dropped 10 spots (#542 → #552)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 561 spots (#1103 → #542)
2026-09-07
HVTrust Changed
HVTrust up 21.0pts (40.2 → 61.2)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1086 → #1103)
2026-09-05
Rank Moved
Rank dropped 41 spots (#1045 → #1086)
2026-09-04
Rank Moved
Rank dropped 24 spots (#1021 → #1045)
2026-09-03
Rank Moved
Rank dropped 57 spots (#964 → #1021)
2026-09-02
Rank Moved
Rank dropped 47 spots (#917 → #964)
2026-09-01
Rank Moved
Rank dropped 36 spots (#881 → #917)
2026-08-31
Rank Moved
Rank dropped 31 spots (#850 → #881)
2026-08-30
Rank Moved
Rank dropped 35 spots (#815 → #850)
2026-08-29
Rank Moved
Rank dropped 49 spots (#766 → #815)
2026-08-28
Rank Moved
Rank dropped 26 spots (#740 → #766)
2026-08-27
Rank Moved
Rank dropped 21 spots (#719 → #740)
2026-08-26
Rank Moved
Rank dropped 99 spots (#620 → #719)
2026-08-19
Rank Moved
Rank dropped 13 spots (#603 → #616)
2026-08-10
Rank Moved
Rank dropped 10 spots (#590 → #600)
2026-08-08
Newly Listed
First tracked at rank #591
GitHub → Website → npm: openclaw-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 68.1 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/openclaw-mcp-server.svg)](https://hvtracker.net/agents/openclaw-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/openclaw-mcp-server"><img src="https://hvtracker.net/badge/openclaw-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON