OpenClaw/clawhub-security-signals huggingface dataset:
Skill: strykragent/prismapi-sdk (version 0.2.1)

--- name: prismapi-sdk description: Elite Agentic Finance SDK for OpenClaw, Claude & Autonomous Trading Bots. Real-time market data, canonical asset resolution, 100+ endpoints for crypto, DeFi, stocks. Sub-50ms latency. homepage: https://prismapi.ai metadata: {"clawdbot":{"emoji":"💎","requires":{"bins":["node"],"env":[]}}} --- # PRISM API SDK The elite agentic finance toolkit. Drop-in market intelligence for AI agents, Claude Code, Cursor, or autonomous trading bots. ## Quick Start ```bash npm install prismapi-sdk ``` ```typescript import { PrismClient } from 'prismapi-sdk'; const prism = new PrismClient({ [REDACTED_SECRET]' }); // Resolve any symbol to canonical data (sub-50ms) const btc = await prism.resolve('BTC'); // → { canonical: 'BTC', name: 'Bitcoin', price: 71514.84, confidence: 0.97 } // Batch resolve for trading agents const assets = await prism.resolveBatch(['BTC', 'ETH', 'AAPL', 'SOL']); // Get family (wrapped tokens, derivatives) const family = await prism.getFamily('BTC'); // → [BTC, WBTC, cbBTC, tBTC, renBTC] ``` ## Key Features | Feature | Description | |---------|-------------| | **Canonical Resolution** | Resolve any ticker, contract, or symbol to single source of truth | | **Sub-50ms Latency** | Cache-first architecture with 4-layer resolution | | **100+ Endpoints** | Crypto, DeFi, stocks, forex, macro, predictions | | **Family Grouping** | BTC → WBTC, cbBTC, tBTC in one query | | **MCP-Native** | Built for OpenClaw, Claude, function calling | ## API Categories - **Resolution** (12 endpoints) - Symbol disambiguation, batch resolve, family grouping - **Crypto** (35+ endpoints) - Prices, markets, OHLCV, metadata - **TradFi** (30+ endpoints) - Stocks, ETFs, forex, financials - **DEX** (25+ endpoints) - Pairs, pools, trending tokens - **DeFi** - Yields, protocols, TVL - **Predictions** - Polymarket, Kalshi, sports odds ## Security Notes - **Read-only API** — fetches public market data only - **No wallet access** — does not interact with wallets or private keys - **No trading** — cannot execute trades - **Data only** — returns JSON market data ## Links - **Docs:** https://prismapi.ai/docs - **npm:** https://www.npmjs.com/package/prismapi-sdk - **GitHub:** https://github.com/Strykr-Prism/PRISM-OS-SDK


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: chinasong/gougoubi-market-orchestrator (version 1.0.1)

--- name: gougoubi-market-orchestrator description: Orchestrate end-to-end Gougoubi market operations by routing to the right skill for creation, activation, risk LP, result submission, reward claiming, or recovery. Use when users describe a high-level market task rather than a single low-level action. metadata: pattern: inversion interaction: multi-turn domain: gougoubi-pbft outputs: structured-json clawdbot: emoji: "🧭" os: ["darwin", "linux", "win32"] --- # Gougoubi Market Orchestrator Use this skill as the top-level router for Gougoubi PBFT workflows. ## Use This Skill When - The user describes a complete market workflow. - The request spans multiple stages such as create, activate, add LP, settle, and claim. - The agent needs to decide which Gougoubi skill to invoke next. ## Routing Rules Map the user intent to one or more skills: - Create proposal: `gougoubi-create-prediction` - Create condition: `gougoubi-create-condition` - Activate only: [REDACTED_SECRET] - Activate + risk LP: [REDACTED_SECRET] - Submit results: `gougoubi-submit-real-results` - Claim rewards: `gougoubi-claim-all-rewards` - Repair partial failures: `gougoubi-recovery-ops` ## Inversion Flow Phase 1: Identify the current market stage: - proposal creation - condition creation - activation - liquidity staking - result submission - reward claiming - recovery Phase 2: Detect missing prerequisites: - proposal exists or not - condition exists or not - committee ready or not - result already submitted or not - rewards claimable or not Phase 3: Choose the smallest correct downstream skill and execute it. Phase 4: Return a compact operation summary: - selected skill - why it was selected - inputs passed through - outcome - recommended next action ## Checkpoints - Do not use this skill to reimplement downstream logic. - Keep routing explicit and auditable. - Prefer the smallest skill that fully solves the current stage. ## Output ```json { "ok": true, "selectedSkill": "gougoubi-activate-and-stake-risklp", "reason": "user asked to activate proposal and add fixed risk LP", "stage": "activation-and-liquidity", "nextAction": "submit results after deadline", "result": {} } ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: bmdhodl/aws-infra (version 1.0.0)

--- name: aws-infra description: Chat-based AWS infrastructure assistance using AWS CLI and console context. Use for querying, auditing, and monitoring AWS resources (EC2, S3, IAM, Lambda, ECS/EKS, RDS, CloudWatch, billing, etc.), and for proposing safe changes with explicit confirmation before any write/destructive action. --- # AWS Infra ## Overview Use the local AWS CLI to answer questions about AWS resources. Default to read‑only queries. Only propose or run write/destructive actions after explicit user confirmation. ## Quick Start 1. Determine profile/region from environment or `~/.aws/config`. 2. Start with identity: - `aws sts get-caller-identity` 3. Use read‑only service commands to answer the question. 4. If the user asks for changes, outline the exact command and ask for confirmation before running. ## Safety Rules (must follow) - Treat all actions as **read‑only** unless the user explicitly requests a change **and** confirms it. - For any potentially destructive change (delete/terminate/destroy/modify/scale/billing/IAM credentials), require a confirmation step. - Prefer `--dry-run` when available and show the plan before execution. - Never reveal or log secrets (access keys, session tokens). ## Task Guide (common requests) - **Inventory / list**: use `list`/`describe`/`get` commands. - **Health / errors**: use CloudWatch metrics/logs queries. - **Security checks**: IAM, S3 public access, SG exposure, KMS key usage. - **Costs**: Cost Explorer / billing queries (read‑only). - **Changes**: show exact CLI command and require confirmation. ## Region & Profile Handling - If the user specifies a region/profile, honor it. - Otherwise use `AWS_PROFILE` / `AWS_REGION` if set, then fall back to `~/.aws/config`. - When results are region‑scoped, state the region used. ## References See `references/aws-cli-queries.md` for common command patterns. ## Assets - `assets/icon.svg` — custom icon (dark cloud + terminal prompt)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: terryso/de-ai-flavor (version 1.0.0)

--- name: de-ai-flavor description: 检查并优化中文文章的AI翻译腔，让文本更自然 argument-hint: <file-path> (要检查的中文 Markdown 文件路径) --- # 去AI味 检查中文文章中的 AI 翻译腔，给出修改建议并直接优化。 ## 输入 `{ARGUMENT}` 是要检查的文件路径。如果为空，询问用户提供文件路径。 ## 检测规则 逐段扫描文章，检测以下 4 类 AI 翻译腔： ### 规则 1：物理动作动词形容思维 用物理动作来描述抽象思维过程，是英文直译的典型痕迹。 **常见问题词：** 接住、击穿、拆解、锋利、打通、抓住、落地、深耕、赋能、抓手、沉淀、闭环、拉齐、对齐（作动词用时）、链路、痛点、颗粒度 **修改方式：** 换成直接的中文表达，或删掉。 - "拆解这个问题" → "分析这个问题" - "打通全链路" → "完成全部流程" - "赋能开发者" → "帮开发者" ### 规则 2：形容词预判 + 冒号 先给一个主观评价，再用冒号展开内容。AI 特别爱用这种结构。 **典型模式：** - "X 很简单：" - "X 有几个亮点：" - "X 最让人印象深刻的是：" - "X 的核心理念是：" - "X 清晰分层：" **修改方式：** 删掉评价部分，直接展开内容。 - "SDK 的架构清晰分层：" → "SDK 的架构分了几层：" - "就这么简单。`prompt()` 是阻塞式的" → "`prompt()` 是阻塞式的" - "这是最让人印象深刻的特性之一" → 直接说内容 ### 规则 3：抽象名词主语 + 形容词结论 用抽象名词做主语，配上一个形容词结论，看起来高级但空洞。 **典型模式：** - "X 的设计哲学不是 A 而是 B" - "X 为 Y 生态带来了一套完整的 Z" - "X 提供了一套生产级别的 Y" - "这些是在构建 Z 时必不可少的基础设施" **修改方式：** 换成具体描述，或直接说结论。 - "它的设计哲学不是做一个简单的封装，而是提供一套生产级别的运行时" → "它提供的不只是 LLM API 的一层封装" - "值得一试" → "可以 clone 下来跑跑看"（给具体动作） ### 规则 4：不必要的英文混入 中英文夹杂在技术文章中有时必要，但有些混入是多余的。 **判断标准：** 如果有对应的中文名称且读者普遍熟悉，就不需要英文。 - "Interface" → "接口"（如果上下文都是中文） - "Leverage" → 直接用中文 **注意：** 技术术语保留英文是正常的（API、SDK、LLM、Agent、MCP 等），不要过度修改。 ## 执行流程 1. **读取文件**：读取 `{ARGUMENT}` 指定的文件 2. **逐段扫描**：按上面 4 条规则逐段检查，记录所有问题 3. **汇报问题**：列出发现的问题，按规则分类，每条给出原文和修改建议 4. **应用修改**：直接修改文件 5. **显示 diff**：用 git diff 展示改动，让用户确认 ## 输出格式 先汇报问题，格式如下： ``` 规则 X：<规则名称> - 第 N 段："原文片段" → 建议改为："修改后" ``` 然后直接应用修改，最后显示 diff。 ## 注意事项 - 只修改有问题的句子，不要改写没有 AI 味的正常内容 - 技术术语的英文保留不动 - 保持文章原有的结构和排版 - 如果文章几乎没有 AI 味，直接告诉用户"这篇文章没什么 AI 味，不需要改"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: hopeatina/orgx-design-agent (version 1.0.0)

--- name: orgx-design-agent description: OrgX design execution contract for OpenClaw. Use for UI/UX changes, design-system alignment, accessibility, and QA evidence capture. version: 1.0.0 user-invocable: true tags: - design - orgx - openclaw --- # OrgX Design Agent (OpenClaw) This skill defines how the OrgX Design agent behaves when running inside OpenClaw. ## Persona - Voice: precise, tasteful, kind. Avoid generic UI and default patterns. - Autonomy: iterate within constraints; ship evidence (desktop + mobile). - Consideration: protect coherence of the design system; accessibility is baseline. ## Primary Contract - Match the existing design system. Do not invent a new one. - Avoid “UI slop”: inconsistent spacing/radii, random gradients, noisy borders. - Mobile is not optional: verify 375px layout. ## Verification Standard For UI changes: - Use the repo’s Playwright / QA capture tooling when available. - Verify the specific states touched (loading/error/empty, scroll/sticky, modals). - Do not claim “verified” unless an actual command ran. ## Reporting Protocol (OrgX) - `orgx_emit_activity` for intent/execution/review/completed. - `orgx_request_decision` for the default-safe human approval path. - Use `orgx_apply_changeset` only when your scope explicitly exposes mutation tools.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zj-john/photo-downloader (version 1.0.1)

--- name: photo-downloader description: 批量下载豆瓣电影/电视剧/综艺的剧照和海报。输入片名自动搜索下载，完全自动化，不需要登录。支持缓存去重、反爬延迟。当用户提到"下载剧照"、"获取海报"、"批量下载图片"时使用。 license: MIT compatibility: 需要Node.js环境 metadata: author: zj_john version: 1.1.0 language: zh-CN category: media-download tags: "spider, crawler, image, download, photos, posters, douban" openclaw: requires: bins: ["node", "npm"] install: - id: playwright kind: node package: playwright bins: [] label: "Install Playwright for Node.js" security_warning: | 本工具涉及网页爬取行为，可能受到豆瓣网的服务条款限制。使用前请确保： 1. 遵守豆瓣网的用户协议和爬虫政策 2. 仅用于个人学习、研究和私人用途 3. 不用于大规模爬取、商业用途或公开分发 4. 尊重网站的反爬虫机制和服务条款 5. This tool does not connect to existing browser sessions for privacy --- # 豆瓣剧照与海报批量下载工具 输入电影/电视剧/综艺的名称，自动搜索、提取、批量下载剧照或海报。完全自动化，不需要登录即可使用。 ## 功能支持 ✅ **核心功能**：输入名称 → 自动搜索 → 批量下载剧照/海报 ✅ 支持分类下载：剧照 (`S`) / 海报 (`R`) ✅ 自动滚动加载更多图片 ✅ 缓存去重：已下载的文件自动跳过，支持分批下载 ✅ 随机延迟反爬（800-2000ms） ✅ 正确处理 Referer 防盗链 ✅ 自动处理重定向 ✅ 保存到 `~/.openclaw/output/photo-download/{内容名}/{类型}/` 目录 ## 支持场景 - ✅ 电影剧照和海报下载 - ✅ 电视剧剧照和海报下载 - ✅ 综艺剧照和海报下载 ## 不支持的场景 - ❌ 艺人/影人照片下载（豆瓣影人页面需要登录才能访问，公开API不支持） - 需要登录才能访问的内容 - 大规模批量爬取整个网站（本工具仅适合少量下载） ## 文件说明 | 文件 | 作用 | |------|------| | **auto-download.js** | 推荐使用 - 全自动版本，Playwright无头浏览器自动完成搜索→提取→下载全流程 | | **index.js** | 手动版本 - 纯HTTP请求，不用浏览器，兼容性较差 | | **download.js** | 单页下载 - 只下载单个豆瓣照片页面里的图片，一般用不到 | ## 使用方法 ### 基本用法（推荐） ```bash # 下载默认：5张剧照 node auto-download.js "内容名称" # 指定类型和数量：下载 10 张海报 node auto-download.js "内容名称" R 10 # 指定类型和数量：下载 3 张剧照 node auto-download.js "内容名称" S 3 ``` 参数说明： - 第一个参数：**内容名称**（电影/电视剧/综艺名） - 第二个参数：**类型**，`S` = 剧照（默认），`R` = 海报 - 第三个参数：**数量**，下载多少张，默认 5 张 ## 使用示例 ### 示例1：搜索《十二生肖》成龙电影，下载 2 张海报 ```bash node auto-download.js "十二生肖" R 2 ``` ### 示例2：搜索《人世间》电视剧，下载 2 张剧照 ```bash node auto-download.js "人世间" S 2 ``` ### 示例3：搜索《喜剧之王单口季》综艺，下载 2 张剧照 ```bash node auto-download.js "喜剧之王单口季" S 2 ``` ## 输出示例： ```text ======================================== 🎬 剧照与海报批量下载 (自动无头浏览器版本) 🎬 内容: 人世间 📸 类型: 剧照 📊 批次数量: 2 ======================================== 🔍 Searching for "人世间"... 📍 Connecting to content platform... ✅ Found: "人世间 (2022)" (id: 35207856) rating: 8.4 🔍 Extracting photo ids from page... 🔌 Connecting to existing Chrome failed, starting new browser... 📖 Loading photos page: https://movie.douban.com/subject/35207856/photos?type=S 🖱️ Scrolling to load more photos... Extracted photo IDs: 2864934437, 2864924871, ... ✅ Found 30 photos 💾 Download directory: /Users/xxx/.openclaw/output/photo-download/人世间 (2022)/剧照 📋 Found 0 already downloaded ⬇️ Downloading 2 photos... [1/2] 2864934437... ✅ 100KB [2/2] 2864924871... ✅ 138KB 🏁 Download complete! Success: 2, Failed: 0 📂 Saved to: /Users/xxx/.openclaw/output/photo-download/人世间 (2022)/剧照 💡 There are 28 more photos remaining. To download more, run: node auto-download.js 35207856 S 28 ``` ## 工作原理 豆瓣使用 Referer 防盗链机制来保护图片。本工具通过无头浏览器加载页面提取图片 ID，然后通过 Node.js 构造正确的请求头来下载图片，绕过防盗链保护。 **不需要登录**，公开剧照任何人都可以访问，所以不需要用户登录豆瓣。


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: emasoudy/screen-monitor (version 1.0.1)

--- name: screen-monitor description: Dual-mode screen sharing and analysis. Model-agnostic (Gemini/Claude/Qwen3-VL). metadata: {"clawdbot":{"emoji":"🖥️","requires":{"model_features":["vision"]}}} --- # Screen Monitor This skill provides two ways for the agent to see and interact with your screen. ## 🟢 Path A: Fast Share (WebRTC) *Best for: Quick visual checks, restricted browsers, or non-technical environments.* ### Tools - **`screen_share_link`**: Generates a local WebRTC portal URL. - **`screen_analyze`**: Captures the current frame from the portal and analyzes it with vision. **Usage:** ```bash # Get the link bash command:"{baseDir}/references/get-share-url.sh" # Analyze bash command:"{baseDir}/references/screen-analyze.sh" ``` --- ## 🔵 Path B: Full Control (Browser Relay) *Best for: Deep debugging, UI automation, and clicking/typing in tabs.* ### Setup 1. Run `clawdbot browser extension install`. 2. Load the unpacked extension from `clawdbot browser extension path`. 3. Click the Clawdbot icon in your Chrome toolbar to **Attach**. ### Tools - **`browser action:snapshot`**: Take a precise screenshot of the attached tab. - **`browser action:click`**: Interact with elements (requires `profile="chrome"`). --- ## Technical Details - **Port**: 18795 (WebRTC Backend) - **Files**: - `web/screen-share.html`: The sharing portal. - `references/backend-endpoint.js`: Frame storage server.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: zhouqicf/caniuse (version 1.0.0)

--- name: caniuse description: Query browser compatibility for CSS/JS features using caniuse-cli. Use when user asks about browser support, compatibility, "can I use X", "does X work in IE/Safari/Chrome", or when writing code that might have compatibility concerns. Also trigger when user mentions specific features like flexbox, grid, container queries, or any web API and wants to know browser support status. --- # Browser Compatibility Query Query browser compatibility data for web features using the `caniuse` CLI tool. ## Prerequisites Check Before querying, verify caniuse-cli is installed: ```bash which caniuse || echo "NOT_INSTALLED" ``` If not installed, tell the user: > caniuse-cli is not installed. Install it with: > ```bash > npm install -g @bramus/caniuse-cli > ``` ## Querying Compatibility Run the caniuse command with the feature name: ```bash caniuse <feature-name> ``` **Feature name formats:** - Hyphenated: `caniuse viewport-units` - Quoted phrases: `caniuse "viewport units"` - With special chars: `caniuse @property` **Common feature name mappings** (user term → caniuse query): - `:has()` selector → `css-has` - `:where()` selector → `css-where` - `:is()` selector → `css-matches-pseudo` - container queries → `css-container-queries` (size) or `css-container-queries-style` (style) - CSS nesting → `css-nesting` - subgrid → `subgrid` - aspect-ratio → `css-aspect-ratio` - gap in flexbox → `flexbox-gap` - CSS grid → `css-grid` - flexbox → `flexbox` **JS/API features:** - ES modules → `es6-module` - async/await → `async-functions` - optional chaining → [REDACTED_SECRET] - fetch API → `fetch` - service workers → `serviceworkers` - WebGPU → `webgpu` ## Presenting Results After running the command: 1. **Show the compatibility table** as returned by caniuse 2. **Highlight key findings:** - Which major browsers fully support it - Any browsers with partial support (note the limitations) - Browsers that don't support it at all 3. **Call out important notes** if the output includes numbered notes (these often contain critical info about prefixes, flags, or partial implementations) 4. **Give practical advice** based on the results: - If widely supported: "Safe to use in production" - If partial support: "Works but check the notes for limitations" - If poor support: "Consider a polyfill or fallback" ## Handling Unknown Features If caniuse returns "Nothing was found": 1. **Check the mapping table above** — many features have specific caniuse names (e.g., `:has()` → `css-has`) 2. **Try common prefixes:** - CSS properties: try `css-` prefix (e.g., `css-grid`, `css-variables`) - MDN data: try `mdn-` prefix for JS features 3. **Try variations:** - Remove special characters: `:has()` → `has` or `css-has` - Use hyphens: "container queries" → `container-queries` 4. **If still not found**, tell the user: > This feature might not be in the caniuse database, or uses a different name. > Check https://caniuse.com to find the correct feature name.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: levineam/x-post (version 1.0.1)

--- name: x-post description: Draft X (Twitter) posts for Andrew's audience. Use when asked to write a tweet, X post, or social media post. Creates accessible, engaging content and saves to Obsidian vault. user-invocable: true --- # X Post Drafting Draft X posts for Andrew's audience — smart generalists interested in AI, meaning, technology, and ideas. ## Voice & Audience **Audience:** Normal people of ordinary intelligence. Not technical. Not niche. The kind of person who follows interesting thinkers on X. **Andrew's voice:** - Conversational, direct - Thinks out loud - Uses concrete examples over abstractions - Occasionally provocative — makes people think - No jargon unless defined immediately ## Format Guidelines **Length options:** - **Single post:** Under 280 characters, punchy - **Long post:** 1000-2000 characters, allowed on X now - **Thread:** Multiple connected posts, each stands alone but builds **Structure (for longer posts):** - Hook first — why should anyone care? - Concrete example or story - The insight / shift in perspective - Call to action or question (drives engagement) **Avoid:** - Technical jargon (Obsidian, Kanban, etc. — unless the post is *about* tools) - Insider references - Sounding like a LinkedIn influencer - "Here are 7 tips..." ## Output Save to: `Notes/X Post - [Title].md` Frontmatter: ```yaml --- created: YYYY-MM-DD status: draft type: X Post --- ``` Include: - The draft post itself - `## Drafting Notes` section with any context about tone, angle, or variations to consider **Always add a link to today's journal** under `## 📝 Notes`. ## Process 1. Understand what Andrew wants to say 2. Identify the core insight (one sentence) 3. Find the accessible angle — how would you explain this to a smart friend? 4. Draft with a hook, concrete middle, and engaging end 5. Save to vault and link in journal — Written by Jarvis


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jiwenbing/advisor (version 1.0.0)

--- name: advisor version: 1.0.0 description: Trusted advisor providing balanced, objective guidance on important decisions across business, personal finance, career, and strategy. Use when users need a sounding board, objective perspective, or trusted second opinion before making an important decision. --- # Advisor Your trusted sounding board. Get objective, balanced advice on important decisions — business strategy, career moves, investments, partnerships, or major life choices. No agenda, just clear thinking. ## When to Use - User needs a second opinion on an important decision - User wants to think through the pros and cons of a major choice - User asks "what would you do in my situation?" - User needs an objective perspective on a situation they're too close to - User wants to stress-test their thinking before acting ## How to Use 1. Listen to the full situation without jumping to advice 2. Ask questions to surface assumptions and blind spots 3. Offer balanced analysis of the decision from multiple angles 4. Share honest assessment including risks the user may be underweighting 5. Offer a clear recommendation while respecting the user's autonomy 6. Help the user think, not decide for them ## Examples - "I'm thinking of leaving my stable job to start a company, what do you think?" - "A competitor offered to acquire us — help me think through whether to sell" - "My business partner wants to pivot, I'm not sure — what's your view?"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: edwardrodriguez703-design/book-waxing (version 1.0.1)

--- name: book-waxing description: Book waxing services through Lokuli MCP. Use when user needs to find and book waxing. Triggers on requests like "book a waxing", "find waxing near me", or any waxing service request. --- # uook waxing Book waxing services through Lokuli's MCP server. ## MCP Endpoint ``` https://lokuli.com/mcp/sse ``` Transport: SSE | JSON-RPC 2.0 | POST requests ## Tools ### search ```json { "method": "tools/call", "params": { "name": "search", "arguments": { "query": "waxing", "zipCode": "90640", "maxResults": 20 } } } ``` ### check_availability ```json { "method": "tools/call", "params": { "name": "check_availability", "arguments": { "providerId": "xxx", "serviceId": "yyy", "date": "2025-02-10" } } } ``` ### create_booking ```json { "method": "tools/call", "params": { "name": "create_booking", "arguments": { "providerId": "xxx", "serviceId": "yyy", "timeSlot": "2025-02-10T14:00:00-08:00", "customerName": "John Doe", "customerEmail": "[REDACTED_SECRET]", "customerPhone": "+13105551234" } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)