# Runhooks (npm · @runhooks/mcp)

Schedule and manage recurring and one-off HTTP jobs on Runhooks from your AI agent.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@runhooks/mcp`
- Version: `0.1.11`
- 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-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to runhooks/runhooks-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 963 tokens (~53/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 9% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_job" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Runhooks MCP server?

Runhooks runs locally as an npm package, launched with npx -y @runhooks/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add runhooks-runhooks-mcp -- npx -y @runhooks/mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "runhooks-runhooks-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@runhooks/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add runhooks-runhooks-mcp -- npx -y @runhooks/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add runhooks-runhooks-mcp --command npx --arg -y --arg @runhooks/mcp
```

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "runhooks-runhooks-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@runhooks/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add runhooks-runhooks-mcp -t stdio -c npx -a -y @runhooks/mcp
```

### Other

```json
{
  "mcpServers": {
    "runhooks-runhooks-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@runhooks/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-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 61, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.10 → 0.1.11

### 2026-10-28 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 73, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-22 (score 77, +1)

- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: 48 → 53
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 0.1.7 → 0.1.10
- [functional] Package version: 0.1.7 → 0.1.8

## MCP tools (18)

### `provision_account` (~91 tokens)

Create a new anonymous Runhooks account (no email required) and save its API key locally for reuse. Idempotent: if this server already has a key (from RUNHOOKS_API_KEY or a previous provision), it returns the EXISTING account instead of creating a duplicate. Call this at most once — never to recover from an auth error.

Input parameters:

- `name` (string): Optional display name for the account

### `whoami` (~24 tokens)

Show the currently authenticated Runhooks account (name, plan, API key prefix).

### `rotate_key` (~38 tokens)

Rotate the API key. The old key stops working immediately; the new key is returned, saved locally, and used for the rest of this session.

### `create_job` (~249 tokens)

Create a new scheduled job — an HTTP request fired on a schedule. The schedule.type is one of: "cron" (schedule.expression is a cron string, e.g. "0 9 * * 1,4" for every Monday & Thursday at 09:00 — build/preview expressions at https://runhooks.app/tools/cron-expression-builder; optional IANA schedule.timezone), "interval" (schedule.expression is the number of milliseconds between runs, as a string), or "once" for a single future run (schedule.expression is an ISO-8601 date-time — either an absolute instant like "2026-12-25T14:00:00Z"/with offset, or a naive wall-clock time like "2026-12-25T09:00:00" interpreted in schedule.timezone, defaulting to UTC; the time must be in the future). One-off jobs support the same retries, alerts and logs as recurring jobs.

Input parameters:

- `description` (string)
- `httpConfig` (object, required)
- `name` (string, required)
- `retryPolicy` (object)
- `schedule` (object, required)
- `tags` (array)

### `list_jobs` (~58 tokens)

List your scheduled jobs with optional filters and pagination.

Input parameters:

- `limit` (integer)
- `name` (string): Filter by name (regex)
- `page` (integer)
- `status` (string)
- `tag` (string)

### `get_job` (~23 tokens)

Get a single job by its ID.

Input parameters:

- `id` (string, required)

### `update_job` (~79 tokens)

Update an existing job. Only the fields you provide are changed.

Input parameters:

- `description` (string)
- `httpConfig` (object)
- `id` (string, required)
- `name` (string)
- `retryPolicy` (object)
- `schedule` (object)
- `status` (string)
- `tags` (array)

### `delete_job` (~20 tokens)

Delete a job permanently.

Input parameters:

- `id` (string, required)

### `pause_job` (~25 tokens)

Pause a job — it stops executing until resumed.

Input parameters:

- `id` (string, required)

### `resume_job` (~20 tokens)

Resume a paused job.

Input parameters:

- `id` (string, required)

### `list_executions` (~50 tokens)

List recent executions (run history) for a job.

Input parameters:

- `jobId` (string, required)
- `limit` (integer)
- `page` (integer)
- `status` (string)

### `replay_execution` (~23 tokens)

Re-run a past execution immediately.

Input parameters:

- `executionId` (string, required)

### `get_usage` (~19 tokens)

Show the current plan usage and limits for the account.

### `list_alerts` (~15 tokens)

List your failure-alert configurations.

### `create_alert` (~103 tokens)

Create a failure alert. Fires when a job dead-letters. Channel is email, webhook, or slack.

Input parameters:

- `channel` (string, required)
- `consecutiveFailuresThreshold` (integer)
- `cooldownMinutes` (integer)
- `enabled` (boolean)
- `jobId` (string|null): Scope to one job; omit for all jobs
- `name` (string, required)
- `target` (string, required): Email address, webhook URL, or Slack webhook URL

### `get_alert` (~24 tokens)

Get a single alert configuration by its ID.

Input parameters:

- `id` (string, required)

### `update_alert` (~82 tokens)

Update an alert configuration. Only the fields you provide are changed.

Input parameters:

- `channel` (string)
- `consecutiveFailuresThreshold` (integer)
- `cooldownMinutes` (integer)
- `enabled` (boolean)
- `id` (string, required)
- `jobId` (string|null)
- `name` (string)
- `target` (string)

### `delete_alert` (~20 tokens)

Delete an alert configuration.

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 61
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-11: 49

## Common questions

### What is the Runhooks MCP server?

Runhooks is an MCP server listed in the public MCP registry as io.github.runhooks/runhooks-mcp. Schedule and manage recurring and one-off HTTP jobs on Runhooks from your AI agent. This page covers its npm package (@runhooks/mcp).

### Is the Runhooks MCP server safe to use?

Runhooks scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Runhooks MCP server expose?

Runhooks exposes 18 tools: provision_account, whoami, rotate_key, create_job, list_jobs, and 13 more. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.

### Is the Runhooks MCP server still maintained?

Runhooks is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Runhooks MCP server under?

Runhooks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

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