Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
WebMCP
v1.0.0WebMCP - Enable AI agents to interact with your web applications through structured tools. Implements the WebMCP standard for Next.js/React apps with tool re...
⭐ 0· 829·1 current·1 all-time
by@slemo54
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Name, description, and included files (bridge JS, Next.js templates, example tools, init scripts) are consistent: this is a toolkit for exposing structured 'tools' to AI agents in a browser/Next.js app. The files provided are appropriate for the described purpose.
Instruction Scope
SKILL.md instructs using a CLI (npx webmcp init / npm install -g @webmcp/cli), but the package/CLI binary is not present in the bundle; instead there are shell scripts (init-webmcp.sh, add-tool.sh) for manual initialization. The instructions otherwise stay within the stated purpose (register/unregister tools, dispatch events) and do not attempt to read unrelated system files or environment variables.
Install Mechanism
No install spec is declared (instruction-only). The repository contains helper shell scripts that copy templates into a project; these are safe to inspect and run locally. Nothing in the bundle downloads or executes remote code during install.
Credentials
No environment variables, credentials, or config paths are requested. The tool definitions include authentication-related tools (login/register) that will handle user credentials inside the web app, which is consistent with the stated purpose.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges. It provides client-side assets and scripts which, when run by the developer, write files into a project — this is expected for a scaffolding/template skill.
What to consider before installing
This package is conceptually coherent for adding an agent→web-app bridge, but there are insecure defaults you should be aware of: the browser bridge posts messages with target '*' and the handleMessage code does not perform origin validation (the origin check is commented out). If you install/use this in a web app, only include the bridge on pages where you control both frame/parent origins, or modify the bridge to validate event.origin and restrict allowed origins before acting on messages. Also verify the CLI commands in the README—there is no @webmcp/cli included in the bundle; the repo provides shell scripts (init-webmcp.sh, add-tool.sh) instead. Before deploying to production: 1) add strict origin checks and consider stronger authentication/CSRF protections for mutating tools (login, submitForm, cart operations), 2) avoid exposing sensitive tool handlers in pages that could be framed by untrusted sites, and 3) review any UI code that will actually perform network requests so user credentials or sensitive data are not forwarded to unintended endpoints.Like a lobster shell, security has layers — review code before you run it.
Plugin bundle (nix)
Skill pack · CLI binary · Config
SKILL.mdCLIConfig
Config requirements
State dirs.webmcp
latestvk9760y7aavj52yvtdqah8kc24581hp6e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis