← 返回 Skills 市场
alopez3006

Snipara Mcp

作者 alopez3006 · GitHub ↗ · v0.1.0
cross-platform ⚠ suspicious
1654
总下载
1
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install snipara-mcp
功能描述
Semantic search tool to quickly find answers across multiple code repositories with AI memory of your preferences for faster documentation lookup.
安全使用建议
Things to check before installing/using this skill: - Provenance: The bundle includes full Python source and suggests installation via pip/uvx, but the registry metadata omitted install/env declarations and shows a different version. Verify the publisher (check PyPI package name, the GitHub repo referenced in README, and that snipara.com is the legitimate service) before running pip/npm. - Credentials: The package uses SNIPARA_API_KEY and SNIPARA_PROJECT_ID (and supports OAuth device flow). These are sensitive. Do not reuse high-privilege or long-lived credentials; prefer limited-scope or short-lived keys and revoke after testing. - Local token storage: OAuth tokens are stored at ~/.snipara/tokens.json with owner-only permissions. If you run the login flow, expect a token file to be created — review its contents and clean up when no longer needed. - Client config changes: SKILL.md shows examples of adding the MCP server to client config files (Claude, Cursor, etc.). Those are manual instructions — the package does not need to modify other tools automatically, but if you follow them you are giving that client persistent access to the Snipara MCP server. Only add it to clients you control and trust. - Data persistence on remote service: The skill offers rlm_remember/rlm_recall for storing preferences and 'memory' on Snipara servers. Understand what you store remotely; avoid sending secrets or private tokens to the third-party memory store. - Audit the code (or run in an isolated environment): Because there are metadata inconsistencies and the package will make network calls, consider inspecting the code, running it in a disposable container, or using network egress controls before granting it credentials. If the publisher and package sources check out and you are comfortable with storing a project-scoped API key or using OAuth, the tool's behavior aligns with its stated purpose. If you cannot verify the package origin or you don't want tokens stored remotely or locally, do not install it.
功能分析
Type: OpenClaw Skill Name: snipara-mcp Version: 0.1.0 The skill bundle provides tools for documentation search and AI agent coordination via the Snipara API. The `skill.md` instructions clearly define tool usage without attempting prompt injection or instructing the agent to perform malicious actions. The Python code handles authentication by reading `SNIPARA_API_KEY` and `SNIPARA_PROJECT_ID` from environment variables and securely storing OAuth tokens in `~/.snipara/tokens.json` with appropriate permissions. All network calls are directed to `snipara.com` for legitimate API interactions. The `rlm_read` tool, despite its name, is implemented as an API call to read indexed documentation on the Snipara platform, not arbitrary local files. No evidence of data exfiltration, malicious execution, persistence, or obfuscation was found.
能力评估
Purpose & Capability
The code and SKILL.md describe a documentation/semantic-search MCP client that talks to snipara.com (rlm_* tools, OAuth, API key support). That purpose is coherent with the network calls and tools implemented. However the registry metadata claims no required environment variables or credentials while the code and README clearly require SNIPARA_API_KEY and SNIPARA_PROJECT_ID (and optionally SNIPARA_API_URL/SNIPARA_IGNORE_OAUTH) and will store OAuth tokens in ~/.snipara/tokens.json. Also package versioning is inconsistent: registry shows 0.1.0 while pyproject.toml reports 2.2.0 and __version__ is 2.1.0. These discrepancies are concerning and should be resolved with the publisher before trusting the skill.
Instruction Scope
SKILL.md and README focus on using rlm tools to query pre-indexed docs and instruct the user to install the package and set SNIPARA_API_KEY / SNIPARA_PROJECT_ID. They recommend adding the MCP server to various client config files (Claude, Cursor, etc.). The instructions do not ask the agent to read arbitrary local files beyond what is needed (it will read/write ~/.snipara/tokens.json for OAuth). They do suggest using rlm_remember to store preferences remotely (this persists user preferences to Snipara). Overall the runtime instructions stay within the stated purpose, but they include actions that persist credentials and settings (local token file and remote memory) which users should understand and opt into explicitly.
Install Mechanism
The registry lists 'No install spec — instruction-only skill' yet the bundle includes full Python package sources (pyproject.toml, README, server.py, auth.py, rlm_tools.py) and SKILL.md explicitly instructs pip/npm installation (pip install snipara-mcp, npm install snipara-mcp) and uvx usage. That mismatch (no declared install spec but a distributable package present and explicit install instructions) is an incoherence. The code's dependencies are standard (mcp, httpx) and there are no obvious download-from-untrusted-URL patterns in the included files, but you should verify the package origin (PyPI name, GitHub repo, publisher) before installing.
Credentials
The skill bundle requires and uses secrets but the registry metadata declared none. The code expects SNIPARA_API_KEY or OAuth tokens (and SNIPARA_PROJECT_ID) and will persist OAuth tokens to ~/.snipara/tokens.json. Requiring an API key and project id is proportionate to a cloud search service, but the omission in the declared requirements is a red flag. Also note SNIPARA_API_KEY may be used as an X-API-Key header (legacy) and OAuth tokens are stored and refreshed automatically — treat stored tokens as sensitive.
Persistence & Privilege
The skill does not request 'always: true' and does not modify other skills' configuration. It does implement a persistent MCP stdio server that users are instructed to register in their LLM client configs; it also writes OAuth tokens to ~/.snipara/tokens.json. Those behaviors are consistent with an MCP client and are expected for this functionality, but they do create persistent state (local token file and remote memories) that the user must explicitly authorize.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install snipara-mcp
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /snipara-mcp 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.1.0
Initial release of Snipara MCP – Smart Documentation Search. - Instantly search and query documentation across multiple repositories with semantic search. - Supports AI memory of your preferences and coding decisions across sessions. - Tools provided: rlm_ask, rlm_context_query (keyword/semantic), rlm_multi_project_query, rlm_remember, rlm_recall, and more. - Role-based usage guide for optimal tool selection and error handling. - Free, Pro, Team, and Enterprise plans supported with feature breakdowns. - Simple 2-minute setup and quick start instructions included.
元数据
Slug snipara-mcp
版本 0.1.0
许可证
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Snipara Mcp 是什么?

Semantic search tool to quickly find answers across multiple code repositories with AI memory of your preferences for faster documentation lookup. 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 1654 次。

如何安装 Snipara Mcp?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install snipara-mcp」即可一键安装,无需额外配置。

Snipara Mcp 是免费的吗?

是的,Snipara Mcp 完全免费(开源免费),可自由下载、安装和使用。

Snipara Mcp 支持哪些平台?

Snipara Mcp 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Snipara Mcp?

由 alopez3006(@alopez3006)开发并维护,当前版本 v0.1.0。

💬 留言讨论