io.github.AmrDab/clawdcursor
NPM · CLAWDCURSOR · SCANNED SEP 28
Safe cross-OS desktop control for any AI agent - the fallback execution layer.
Available components
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects file-type 16.5.4, reached via @nut-tree-fork/nut-js > jimp > @jimp/custom > @jimp/core > file-type. A fixed version is available. View diagnostics → Fail
- Install-script check failed: the install command fetches or executes arbitrary code (pipe_to_shell,inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 106 of 274 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
How do I install the io.github.AmrDab/clawdcursor MCP server?
io.github.AmrDab/clawdcursor runs locally as an npm package, launched with npx -y clawdcursor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · clawdcursor
claude mcp add amrdab-clawdcursor -- npx -y clawdcursor
{
"mcpServers": {
"amrdab-clawdcursor": {
"command": "npx",
"args": [
"-y",
"clawdcursor"
]
}
}
} {
"servers": {
"amrdab-clawdcursor": {
"command": "npx",
"args": [
"-y",
"clawdcursor"
]
}
}
} codex mcp add amrdab-clawdcursor -- npx -y clawdcursor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"amrdab-clawdcursor": {
"type": "local",
"command": [
"npx",
"-y",
"clawdcursor"
],
"enabled": true
}
}
} openclaw mcp add amrdab-clawdcursor --command npx --arg -y --arg clawdcursor
mcp_servers:
amrdab-clawdcursor:
command: "npx"
args: ["-y", "clawdcursor"] {
"McpServers": {
"amrdab-clawdcursor": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"clawdcursor"
]
}
}
} assistant mcp add amrdab-clawdcursor -t stdio -c npx -a -y clawdcursor
{
"mcpServers": {
"amrdab-clawdcursor": {
"command": "npx",
"args": [
"-y",
"clawdcursor"
]
}
}
} 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.
- 28 Sept 26 34
First indexed and scored.
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 28 Sept 2026 · Analysed npm/clawdcursor@1.5.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | node scripts/verify-install.js || node -e "process.exit(0)" && node scripts/postinstall-native.js || node -e "process.exit(0)" |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-5v7r-6r5c-r473 | CVE-2026-31808 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 274 packages
| Packages resolved | 274 |
|---|---|
| Deprecated | 1 |
| Stale | 99 |
| No linked repository | 7 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the io.github.AmrDab/clawdcursor MCP server?
io.github.AmrDab/clawdcursor is an MCP server listed in the public MCP registry as io.github.AmrDab/clawdcursor. Safe cross-OS desktop control for any AI agent - the fallback execution layer. This page covers its npm package (clawdcursor).
Is the io.github.AmrDab/clawdcursor MCP server safe to use?
io.github.AmrDab/clawdcursor scores 34 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 28 September 2026. It declares an install script we flagged as high risk. 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.
Is the io.github.AmrDab/clawdcursor MCP server still maintained?
io.github.AmrDab/clawdcursor is still listed as active in the MCP registry. We last reached this channel on 28 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 io.github.AmrDab/clawdcursor MCP server under?
io.github.AmrDab/clawdcursor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.