Store Mcp Connect

Connect an AI agent to a Mobazha store via MCP (Model Context Protocol). Use when the user wants their agent to directly manage store products, orders, and s...

This skill appears to do what it says (connect an AI agent to a Mobazha store) but there are important gaps you should consider before installing: - Metadata mismatch: the SKILL.md requires an API token and optionally SSH credentials, but the registry entry lists no required credentials. Assume the skill needs a Bearer API token and plan accordingly. - Minimize scope: create the least-privilege API token possible (read-only or scoped to only the actions the agent needs) before connecting. Test with a read-only token first. - Secret handling: follow the skill's own advice—store tokens in environment variables or a secrets manager, not in source-controlled config files. If you must add tokens to agent config files, ensure those files are excluded from VCS and have appropriate filesystem permissions. - Admin/password use: only run token-generation curl commands on machines you control; avoid pasting admin passwords into third-party UIs or untrusted agents. - Verify endpoints and provenance: confirm the SSE URL you configure actually belongs to your store (and not a typo or malicious domain). Because the skill has no homepage and unknown source, prefer manual verification and avoid downloading binaries unless from an official Mobazha release (e.g., official Docker image or GitHub release). - If you permit SSH tunneling, ensure the SSH key/credentials are tightly controlled and that you understand the tunnel's implications. If you want, provide the registry/package metadata or a link to an official Mobazha documentation page; with that I can re-evaluate and raise or lower the concern level.

Type: OpenClaw Skill Name: mobazha-store-mcp-connect Version: 0.2.0 The skill bundle consists of documentation (SKILL.md) providing instructions for connecting an AI agent to a Mobazha store using the Model Context Protocol (MCP). It includes configuration examples for various agents, security best practices for handling API tokens, and a list of available management tools. No executable code is provided, and the instructions are transparent, defensive, and aligned with the stated purpose of store integration.