# Impri (npm · @impri/mcp)

Impri MCP server — human-in-the-loop approval inbox for AI agents

- Trust score: 62/100 (medium)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@impri/mcp`: 62/100 (this document), [markdown](https://verifymcp.io/servers/sekera-radim-impri/impri-mcp.md), [page](https://verifymcp.io/servers/sekera-radim-impri/impri-mcp)

## Channel facts

- Registry: `npm`
- Package: `@impri/mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1756 tokens (~219/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add sekera-radim-impri -- npx -y @impri/mcp
```

### Codex

```bash
codex mcp add sekera-radim-impri -- npx -y @impri/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sekera-radim-impri": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@impri/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sekera-radim-impri --command npx --arg -y --arg @impri/mcp
```

### Hermes

```yaml
mcp_servers:
  sekera-radim-impri:
    command: "npx"
    args: ["-y", "@impri/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "sekera-radim-impri": {
      "command": "npx",
      "args": [
        "-y",
        "@impri/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 62, +29)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 33, +28)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 6, −37)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (8)

### `impri_push_action` (~438 tokens)

Submit an action to the Impri human-approval inbox.

The action appears in the operator's web and mobile inbox as a card with a title, formatted preview, and optional tap-to-edit fields. The operator approves or rejects with one tap; you poll for the decision with impri_await_decision.

Returns { action_id, status: "pending", inbox_url }. Save action_id — you need it for all follow-up calls.

Example — send a draft Reddit reply for review:
  kind: "reddit.comment"
  title: "Reply: Why is resume advice so conflicting?"
  preview: { format: "markdown", body: "The advice conflicts because different advisors optimise for different audiences..." }
  target_url: "https://reddit.com/r/cscareerquestions/comments/..."
  editable: ["preview.body"]   // lets the reviewer tweak wording before approving

Input parameters:

- `editable` (array): Dot-notation fields the reviewer may edit before approving (e.g. ['preview.body']). The final edited values are echoed back in the approved action.
- `expires_in` (number): Seconds until the action auto-expires (default 86400 = 24 h). After expiry the status becomes 'expired' and no decision can be made.
- `idempotency_key` (string): Stable key to prevent duplicate submissions on retry. The same key within 24 h returns the original action instead of creating a new one.
- `kind` (string, required): Taxonomy label used for inbox filtering (e.g. 'reddit.comment', 'email.send', 'blog.publish'). Free-form; choose a consistent scheme.
- `payload`: Opaque data echoed back in the webhook callback — useful for storing context (e.g. Reddit post id, draft id, queue position). Not shown to the reviewer.
- `preview` (object, required): The content the reviewer reads before deciding.
- `target_url` (string): URL the reviewer can open for context (e.g. the Reddit thread, the email draft). Optional but strongly recommended.
- `title` (string, required): Short headline shown in the inbox card. Keep it under 120 characters.

### `impri_await_decision` (~251 tokens)

Poll until the human approves, rejects, or the timeout elapses.

Checks GET /actions/:id every 5 seconds and returns as soon as the action leaves the pending state.

Decision meanings:
  "approved"  — proceed with the action; any reviewer edits are included in preview/payload
  "rejected"  — abort; respect the decision and do not proceed
  "expired"   — the approval window closed; create a new action if the task is still relevant

On timeout the action stays pending in the inbox. Call impri_inbox_status to check queue depth and consider pausing further submissions.

Typical usage:
  1\. impri_push_action → get action_id
  2\. impri_await_decision(action_id) → wait for human decision
  3\. If approved: execute the action, then impri_report_result(action_id, "executed")

Input parameters:

- `action_id` (string, required): The id returned by impri_push_action.
- `timeout_s` (number): Maximum seconds to wait before returning (default 300 — 5 minutes). After timeout the action is still pending; retry or call impri_inbox_status.

### `impri_report_result` (~139 tokens)

Report whether you successfully executed an approved action.

Closes the audit loop — the operator sees 'executed' or 'execute_failed' in the inbox alongside the original action and decision. Always call this after attempting an approved action, even on failure.

Statuses:
  "executed"       — action was carried out successfully
  "execute_failed" — execution attempt failed (include the error in detail)

Input parameters:

- `action_id` (string, required): The id returned by impri_push_action.
- `detail` (string): Optional message — error description on failure, short confirmation on success.
- `status` (string, required): Outcome of executing the approved action.

### `impri_inbox_status` (~68 tokens)

Check how many actions are waiting for human decisions.

Returns the pending count and a brief list of pending action titles. Call this before starting a large batch of tasks — if the inbox is backed up, pause and let the operator catch up to avoid actions expiring before they are reviewed.

### `impri_create_watcher` (~227 tokens)

Create a watcher that monitors external sources (RSS feeds, Reddit, URL diffs) and delivers matching items to the approval inbox or a webhook.

The watcher runs on the schedule you specify, deduplicates items by URL/content-hash, and delivers only new matches. The first run establishes a baseline and does not generate alerts.

Example — watch an RSS feed for AI-related news:
  spec: {
    name: "AI launches radar",
    kind: "rss",
    config: { url: "https://openai.com/news/rss.xml" },
    keywords: ["launch", "gpt-", "voice"],
    keywords_none: ["funding", "benchmark"],
    min_score: 1,
    schedule: { every: "8h", jitter: "4h" }
  }

Returns { watcher_id, name, kind, status, next_run_at }.

Input parameters:

- `spec` (object, required): Watcher specification (name, kind, config, keywords, keywords_none, min_score, schedule). See SPEC.md §3.2 for the full schema.

### `impri_list_watchers` (~84 tokens)

List all configured watchers, optionally filtered by status.

Returns the watcher count and a summary line per watcher (id, name, kind, status). Use this to audit what is being monitored, check for degraded watchers, or find a watcher_id for further operations.

Input parameters:

- `status` (string): Filter watchers by status. Omit to return all watchers regardless of status.

### `impri_list_watcher_presets` (~174 tokens)

List all available watcher presets with their parameters.

Presets are pre-configured watcher templates for common sources (Hacker News, Reddit, GitHub, npm, YouTube, arXiv, etc.). Each preset has an id, a human-readable title, required and optional params, and a default schedule.

Call this first to discover which preset fits your monitoring goal, then use impri_create_watcher_from_preset to create the watcher by supplying only the preset_id and param values. No deep knowledge of watcher config schemas is needed.

Example output:
  Community:
    - hn-front-page: "Hacker News Front Page" (rss) — no params required
    - reddit-keyword: "Reddit – Keyword Search" (reddit_search) — params: query, [subreddit]

### `impri_create_watcher_from_preset` (~375 tokens)

Create a watcher from a preset template by supplying the preset id and param values.

Presets handle all watcher config construction — URL building, keyword setup, SSRF validation — so you only provide the param values listed by impri_list_watcher_presets.

The schedule defaults to the preset's recommended interval but can be overridden. The name defaults to "{preset title}: {primary param value}" if omitted.

Returns { watcher_id, name, kind, status, next_run_at }.

Examples:

  Watch the HN front page (no params needed):
    preset_id: "hn-front-page"
    params: {}

  Watch a subreddit for new posts:
    preset_id: "reddit-subreddit"
    params: { subreddit: "MachineLearning" }

  Watch a GitHub repo for new releases, check every 2 hours:
    preset_id: "github-releases"
    params: { owner: "fastify", repo: "fastify" }
    schedule: { every: "2h" }

  Watch HN for keyword with a custom min_points threshold:
    preset_id: "hn-keyword"
    params: { keyword: "rust programming", min_points: "25" }

Input parameters:

- `name` (string): Optional display name for the watcher. Defaults to "{preset title}: {primary param value}" when omitted.
- `params` (object, required): Key/value map of param values as strings. Required params must be present; optional params may be omitted to use preset defaults.
- `preset_id` (string, required): Preset identifier from impri_list_watcher_presets (e.g. "hn-front-page", "reddit-subreddit", "github-releases").
- `schedule` (object): Optional schedule override. Omit to use the preset's default schedule.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/sekera-radim-impri/impri-mcp#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 33
- 2026-07-31: 5
- 2026-07-30: 6
- 2026-07-28: 43
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/@impri/mcp
- Socket report: https://socket.dev/npm/package/@impri/mcp
- Repository: https://github.com/sekera-radim/impri
- Website: https://impri.dev/
- Changelog RSS feed: https://verifymcp.io/servers/sekera-radim-impri/impri-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/sekera-radim-impri/impri-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/sekera-radim-impri/impri-mcp