io.github.soteeabam/looppause
NPM · @LOOPPAUSE/MCP
LoopPause MCP server — pause agent execution and route human approval requests
Available components
Last scanned (19 hours ago)
Scores higher than 79% of npm servers
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 72 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 229 tokens (~114/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_approval" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 93. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −2
- Stability: pass → 0.80 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/@looppause/mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_approval ~76
Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| pause_id | string | yes | The pause_id returned by request_approval. |
No output schema declared.
No examples provided.
request_approval ~153
Send 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action_description | string | yes | What the agent is about to do, in plain English. |
| action_details | object | yes | Key-value details about the action (e.g. amount, vendor, target). String values only. |
| recipient_email | string | – | Email to send the approval request to. |
| recipient_slack | string | – | Slack channel or user ID (e.g. #approvals or U12345). |
| timeout_hours | number | – | Hours before the request expires. Max 168. |
No output schema declared.
No examples provided.
How do I install the io.github.soteeabam/looppause MCP server?
io.github.soteeabam/looppause runs locally as an npm package, launched with npx -y @looppause/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @looppause/mcp
claude mcp add soteeabam-looppause -- npx -y @looppause/mcp
What is the io.github.soteeabam/looppause MCP server?
io.github.soteeabam/looppause is an MCP server listed in the public MCP registry as io.github.soteeabam/looppause. LoopPause MCP server, pause agent execution and route human approval requests. This page covers its npm package (@looppause/mcp).
Is the io.github.soteeabam/looppause MCP server safe to use?
io.github.soteeabam/looppause scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.soteeabam/looppause MCP server expose?
io.github.soteeabam/looppause exposes 2 tools: request_approval, check_approval. Their descriptions and schemas cost roughly 229 tokens of context every time the server is loaded.
Is the io.github.soteeabam/looppause MCP server still maintained?
io.github.soteeabam/looppause is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.soteeabam/looppause MCP server under?
io.github.soteeabam/looppause declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.