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 分

    請在儲存庫或註冊中心條目中宣告授權條款。