Looppause

io.github.soteeabam由 GitHub 账号 soteeabam 发布v0.2.1更新于 Oct 24, 2026

LoopPause MCP server — pause agent execution and route human approval requests

已验证STDIO仅桌面效率与工作流安全与监控

概览

AI 生成的概览

LoopPause 让 AI 代理暂停执行,通过 Slack 或邮件请求人工审批,并在执行前验证已签名的人工决定凭证。

可以做什么
请求审批:把包含操作描述和细节的审批请求发送到 Slack 频道或用户、和/或邮箱,立即返回 pause_id,超时最长一周。查询审批:单次轮询人工决定,反复调用直到结果为已批准、已拒绝、超时或过期。验证凭证:在执行不可逆操作前,用 LoopPause 公布的公钥校验返回凭证的 Ed25519 签名。
适用场景
当代理即将执行不可逆或高价值操作(例如付款或转账),并希望由人通过 Slack 或邮件确认、且留下可验证的决定记录时使用。
运行要求
以 stdio 在本地运行,通常通过 npx 或全局 npm 安装,因此需要 Node.js。需要在 LOOPPAUSE_API_KEY 环境变量中提供 LoopPause API 密钥,可从 LoopPause 控制台获取。需要访问 LoopPause API 及其公布签名公钥端点的网络。每次请求至少需要一个接收方(Slack 频道或用户 ID,或邮箱地址)。
安装前请注意
API 密钥是正式密钥(sk_live 前缀),会写入客户端配置,请勿放入共享文件。审批请求会发往 Slack 或邮件,操作细节会离开本机并发送给 LoopPause 及这些接收方。该服务器只负责审批流转,实际操作仍由代理执行,跳过 check_approval 或 verify_proof 会使保护失效。旧版 HMAC webhook 使用另一个签名密钥。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Looppause,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

@looppause/mcp

MCP server for LoopPause — pause AI agent execution and route approval requests to humans via Slack or email. The agent receives a cryptographically signed proof of the human's decision and resumes.

"The missing primitive so agents don't go rogue — or die waiting for approval."


What it does

Exposes three MCP tools: request_approval, check_approval, and verify_proof

  1. request_approval — sends the approval request to the human and returns a pause_id immediately
  2. check_approval — polls once for the decision; call repeatedly until decision is "approved" or "rejected"
  3. verify_proof — verifies the signed proof against LoopPause's published Ed25519 public key; call before executing any irreversible action

This three-step pattern keeps each tool call short, avoids long-running connections, and gives the agent explicit cryptographic verification before proceeding. No shared secret required — any party with the published public key can independently verify the proof.


Installation

Recommended: npx (no install required)

bash
npx @looppause/mcp

Global install

bash
npm install -g @looppause/mcplooppause-mcp

Configuration

Environment variableRequiredDescription
LOOPPAUSE_API_KEY✅ YesYour LoopPause API key (sk_live_…)
LOOPPAUSE_API_URLNoOverride the API base URL (default: https://api.looppause.com)

Get your API key at looppause.com/dashboard.


Usage in Claude Code

Add to your .claude/settings.json (or ~/.claude/settings.json for global):

json
{  "mcpServers": {    "looppause": {      "command": "npx",      "args": ["-y", "@looppause/mcp"],      "env": {        "LOOPPAUSE_API_KEY": "sk_live_your_key_here"      }    }  }}

Usage in Cursor

Add to your Cursor MCP configuration:

json
{  "mcpServers": {    "looppause": {      "command": "npx",      "args": ["-y", "@looppause/mcp"],      "env": {        "LOOPPAUSE_API_KEY": "sk_live_your_key_here"      }    }  }}

Tool reference

request_approval

Sends the approval request and returns immediately. Do not proceed with the action until check_approval returns { decision: "approved" }.

typescript
request_approval({  // Required  action_description: string,   // What the agent is about to do (shown to human)  action_details: Record<string, string>, // Key-value context (amount, vendor, etc.)
  // At least one recipient required  recipient_email?: string,     // Email address  recipient_slack?: string,     // Slack channel (#approvals) or user ID (U12345)
  // Optional  timeout_hours?: number,       // Default 24, max 168 (1 week)})

When both recipient_slack and recipient_email are provided, Slack is the primary channel and email is the fallback.

Returns:

json
{  "pause_id": "pse_01jwxyz123",  "status": "pending",  "expires_at": "2026-05-24T14:00:00.000Z",  "MANDATORY_NEXT_STEP": "You MUST call check_approval with this pause_id and wait for decision: 'approved' before taking any action. Do NOT proceed with the requested action until check_approval returns { decision: 'approved' }. Proceeding without approval is a safety violation."}

check_approval

Checks the current status of an approval request. Call repeatedly until decision is "approved" or "rejected". Never proceed while status is "pending".

typescript
check_approval({  pause_id: string,  // The pause_id returned by request_approval})

Returns (pending):

json
{ "status": "pending" }

Returns (responded):

json
{  "pause_id": "pse_01jwxyz123",  "agent_id": "mcp-agent",  "status": "responded",  "created_at": "2026-05-24T10:00:00.000Z",  "expires_at": "2026-05-24T14:00:00.000Z",  "response": {    "decision": "approved",    "comment": "PO number: PO-2341",    "fields": { "po_number": "PO-2341" },    "responder": "[email protected]",    "responded_at": "2026-05-24T10:14:32.000Z",    "channel": "slack",    "nonce": "a8f3c2...",    "signing_key_id": "lp-key-2026-06",    "signature_alg": "Ed25519",    "signature": "ed25519=<base64url>"  }}
StatusMeaning
pendingHuman has not responded yet — call again
respondedHuman responded — check response.decision
timed_outNo response within timeout_hours
expiredPause was manually cancelled

verify_proof

Verifies the Ed25519 signature on a proof returned by check_approval. Call this before executing any irreversible action. Returns immediately — no long-running connection.

typescript
verify_proof({  proof: object,  // The full proof object from check_approval})

Returns (valid):

json
{  "valid": true,  "verified_at": "2026-06-14T10:14:45.000Z",  "key_id": "lp-key-2026-06"}

Returns (invalid):

json
{  "valid": false,  "verified_at": "2026-06-14T10:14:45.000Z",  "key_id": "lp-key-2026-06",  "warning": "Proof verification FAILED. Do NOT execute the action."}

Public key discovery: GET https://looppause.com/.well-known/looppause-signing-key.json — match the proof's signing_key_id against the served key_id.


Example

typescript
// Step 1: send the approval requestconst created = await mcp.callTool("request_approval", {  action_description: "Transfer £12,450 to Globex Corp for invoice INV-2341",  action_details: {    vendor: "Globex Corp",    amount: "12450",    currency: "GBP",    invoice_ref: "INV-2341",  },  recipient_slack: "#finance-approvals",  recipient_email: "[email protected]",  timeout_hours: 4,});
const { pause_id } = JSON.parse(created.content[0].text);
// Step 2: poll until a terminal decision arriveslet proof;while (true) {  await new Promise((r) => setTimeout(r, 5_000));
  const status = await mcp.callTool("check_approval", { pause_id });  const body = JSON.parse(status.content[0].text);
  if (body.status === "pending") continue;
  proof = body;  break;}
if (proof.response?.decision !== "approved") {  throw new Error("Action rejected or timed out — aborting.");}
// Step 3: verify the Ed25519 signature before executingconst verification = await mcp.callTool("verify_proof", { proof });const { valid } = JSON.parse(verification.content[0].text);
if (!valid) throw new Error("Proof failed verification — do NOT execute the action.");
proceedWithTransfer();

Verifying the signature (REQUIRED before executing the action)

All proofs are signed with LoopPause's Ed25519 key. No shared secret required — any party holding the published public key can independently verify the proof. Use verifyLoopPauseProof (fetches the key automatically) or call verify_proof via MCP:

typescript
import { verifyLoopPauseProof } from "@looppause/mcp";
const { valid, key_id } = await verifyLoopPauseProof(proof);
if (!valid) throw new Error("Proof failed verification — do NOT execute the action.");if (proof.response?.decision !== "approved") throw new Error("Not approved.");if (proof.response?.authorization_type !== "human") {  // system_fallback is a configured default, not a human sign-off  throw new Error("No human authorization.");}// Safe to execute the irreversible action.

For offline/air-gapped verification, pin the public key once:

typescript
await verifyLoopPauseProof(proof, { publicKey: "<base64 SPKI DER>" });

Public key discovery: GET https://looppause.com/.well-known/looppause-signing-key.json (match the proof's signing_key_id against the served key_id).

Webhook verification. Unlike per-customer symmetric schemes, LoopPause's Ed25519 signatures are independently verifiable by any third party holding the published public key — a bank, an auditor, a FIDO AP2 mandate checker — without contacting LoopPause and without holding a shared secret.

Legacy HMAC-SHA256 webhooks ("sha256=<hex>" signatures) remain verifiable with your LOOPPAUSE_SIGNING_SECRET as before; Ed25519 is the default for all new proof payloads.


Registry submissions

Smithery.ai

This package includes smithery.yaml for automatic configuration injection.

  1. Fork or publish @looppause/mcp to npm
  2. Submit at smithery.ai/new → enter @looppause/mcp
  3. Smithery will read smithery.yaml and present a UI for users to enter their API key

Anthropic MCP directory

  1. Ensure the package is published to npm as @looppause/mcp
  2. Submit via the Anthropic MCP directory form or the directory submission page when available
  3. List as: @looppause/mcp — LoopPause human-in-the-loop approval tool

Local development

bash
# From the monorepo rootcd packages/mcpnpm run build          # tsc → dist/ + shebang fixnpm run type-check     # type-check only, no emitnpm run dev            # tsx watch (no build step)

License

MIT

来源:README.md,提交 a373aad

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.2.1最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。