Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Let agents use temporary secrets without receiving their values in chat. Local stdio; Node 22+.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 geland 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.0.2)于17天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Give your agent access with a sealed secret.
Let your agent use temporary passwords, tokens, and one-time codes without putting their values in the chat. The local tool opens a private browser page, shows why the agent needs access, and applies secrets to requests you approve. No vault to configure. No Secret Handoff account.
This repository publishes the Claude Code and Codex plugins for the signed Secret Handoff 0.0.4 release. It includes the skill, local stdio MCP configuration, Claude detection hooks, and a status-only Claude card. Secret entry stays in your browser. These are repository plugins, not claims of vendor-curated directory approval.
Install CLI 0.0.4 first. Choose the archive for your platform and verify it with the release's SHA256SUMS. Run secrethandoff setup below to connect Claude Code and Codex when their CLIs are on PATH.
secrethandoff version
secrethandoff setup secrethandoff doctor
The expected version is 0.0.4. In the project where your agent works, run secrethandoff init to add credential guidance. Start a new agent session.
If you prefer to install the plugin yourself after installing the binary:
claude plugin marketplace add geland/secrethandoff-integrations
claude plugin install secrethandoff@secrethandoff
codex plugin marketplace add geland/secrethandoff-integrations
codex plugin add secrethandoff@secrethandoff
Restart the client or start a fresh session after installation. The binary must be on the PATH inherited by the client, including when launching a desktop app. secrethandoff doctor checks the local setup.
For a pinned marketplace, Codex accepts codex plugin marketplace add geland/secrethandoff-integrations --ref v0.0.4. Claude Code accepts the Git source https://github.com/geland/secrethandoff-integrations.git#v0.0.4 with claude plugin marketplace add. The release ZIP is also available for review.
Install the new binary first and verify that secrethandoff version reports 0.0.4. Both plugins launch the binary on your PATH.
claude plugin marketplace update secrethandoff
claude plugin update secrethandoff@secrethandoff
codex plugin marketplace upgrade secrethandoff
codex plugin add secrethandoff@secrethandoff
If your marketplace is pinned, switch its source to v0.0.4 first. Start a fresh agent session after updating. If you opted into Codex command approval, reapply the opt-in as described below.
Ask your agent: “Use Secret Handoff for the temporary credential this task needs.” Enter the value only on the Secret Handoff browser page. Approve a narrow API host, method, and path. The agent uses a reference and receives redacted results. Ask the agent to forget the secret when the task is done.
Secrets live in the tool process's memory until forgotten or the process exits. Filled secrets do not have an automatic expiry timer. Approved APIs receive the value. run_with_secret requires browser command approval by default; an approved command receives the value and can leak it. Owners can opt into verified Claude Code native permission prompts or Codex approval settings; Codex settings may authorize automatically. These modes do not change how secrets are entered.
Claude detection hooks can block some accidental pastes before they reach the model. They cannot erase a value already saved in the client's local transcript. Never paste secrets into chat. Read the security boundaries.
With the supported binary and stable Codex 0.155.1 in the 0.155 series, or the exact desktop build 0.162.0-alpha.17.2, the owner can choose native host-policy authorization. It follows the owner's settings, including allow rules, hooks, and automatic review; a human click is not required in that mode. Browser approval remains the distribution default. Secret entry always stays on the isolated Secret Handoff page.
From a checkout of this repository, reload the plugin, run the owner opt-in helper, then start a fresh chat. The helper is not included in the review ZIP:
codex plugin add secrethandoff@secrethandoff
python3 scripts/configure_codex_approval.py codex \ --plugin-dir ~/.codex/plugins/cache/secrethandoff/secrethandoff/0.0.4
The helper validates and edits only the installed mcp.json and .mcp.json launch environment. It does not change host policies, reviewer, or hooks. Reinstallation resets the opt-in; rerun it after reload. Use browser instead of codex to restore browser command approval. Agents may apply it only when explicitly instructed by the owner.
python3 scripts/check_codex_approval.py tests live allow/deny delivery with a harmless server. python3 scripts/check_codex_approval.py --installed-plugin checks that the real cached plugin starts with native mode and can list a new empty store. Both use child-only isolation and no secrets. Pass --codex-bin /absolute/path/to/codex to either check to validate the desktop bundled executable instead of the terminal CLI. Run python3 -m unittest discover -s tests -p test_codex_approval_config.py for helper preservation and refusal tests. Desktop prompt rendering needs a separate owner-run dummy test. Command results report client_policy / host_policy, never a claim that a human clicked.
request_secrets asks for 2–8 credentials on one local browser page. A group name identifies the request; fields have separate names and optional labels. One policy applies to every field, and all values become ready together. Wait using the group name. Forgetting the group or any member erases all members. Phone/headless relay fill is currently unsupported for groups. Existing request_secret calls still collect one value. This feature does not change command approval settings.
secrethandoff mcp.release-lock.json pins all six platform archives and six MCPB bundle hashes. Plugins start the binary on PATH; metadata does not replace or enforce that binary. Check secrethandoff version before use. Source and release provenance are available in the binary repository.Use Python 3.11+ and Node 24. Install requirements-review.txt in a virtual environment, then run:
python scripts/test_release.py
python scripts/validate.py --release python scripts/package.py --release python scripts/test_package.py
tests/card.test.tsx runs with the Claude mod test runner. tests/card-state.test.mjs runs with Node and TypeScript available through SECRETHANDOFF_TEST_TYPESCRIPT. See 0.0.2 release status, agent evals, and contributor guidance.