Looppause MCP server
io.github.soteeabam/looppause·v0.2.1LoopPause MCP server — pause agent execution and route human approval requests
0 stars25 downloads/wk
Reviews
Write oneNobody has reviewed Looppause yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Looppause tools (2, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_approvalCheck the status of a pending approval request. Call this repeatedly until decision is 'approved' or 'rejected'. Never proceed with the requested action while status is 'pending'. Returns the signed decision when responded, or an error if timed_out/expired.
request_approvalwrite actionSend a human approval request for a sensitive action. Returns a pause_id immediately — do not proceed until check_approval returns approved. Use before payments, deletions, external communications, or other irreversible operations.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 50 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Looppause compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 4,460 AI and agents servers
- Tools
- 2
- the typical AI and agents server has 6
- Tools that change things
- 50%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 25
- more than 11% of 1,538 AI and agents servers with a package
What its tools let an agent do: 1 read · 1 change
Install Looppause in Claude Code, Cursor or VS Code
Runs npx -y @looppause/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add looppause -- npx -y @looppause/mcp
What the publisher says
From the Looppause repository's README, as published. We do not edit it. Read it on GitHub
@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: requestapproval, checkapproval, and verifyproof**
- requestapproval — sends the approval request to the human and returns a pauseid immediately
- checkapproval** — polls once for the decision; call repeatedly until decision is "approved" or "rejected"
- verifyproof** — 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)
npx @looppause/mcpGlobal install
npm install -g @looppause/mcp
looppause-mcpConfiguration
Get your API key at looppause.com/dashboard.
Usage in Claude Code
Add to your .claude/settings.json (or ~/.claude/settings.json for global):
{
"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:
{
"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 checkapproval returns { decision: "approved" }.**
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 recipientslack and recipientemail are provided, Slack is the primary channel and email is the fallback.
Returns:
{
"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".
check_approval({
pause_id: string, // The pause_id returned by request_approval
})Returns (pending):
{ "status": "pending" }Returns (responded):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Looppause: common questions
- Is Looppause MCP server safe?
- Mostly: it is graded B (78/100). Read the Looppause safety report
- How do I install Looppause?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Looppause need an API key?
- Yes. The registry entry asks for
YOUR_API_KEY. - Is Looppause maintained?
- The last commit was 92 days ago (2026-08-04). The latest release is v0.2.1.
- What can I use instead of Looppause?
- Servers from other publishers that do the same job: Emilia Protocol MCP server, CHAP Coordinator MCP server and HOL Guard MCP server.
- How does Looppause compare with other AI and agents MCP servers?
- safety score 78/100 (higher than 57% of 4,460 AI and agents servers); tools 2 (the typical AI and agents server has 6); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Looppause
Same job from other publishers: the closest match first, then the best rated.
- Emilia ProtocolExact-action approval for consequential agent actions: request, track, and verify signed receipts.not reviewedEstablishedB
- CHAP CoordinatorAuditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.not reviewedEstablishedA
- HOL GuardLocal-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.not reviewedEstablishedA
- DecionisAuthorize consequential AI agent actions before executionnot reviewedEstablishedA