Runhooks
NPM · @RUNHOOKS/MCP
Schedule and manage recurring and one-off HTTP jobs on Runhooks from your AI agent.
Available components
Last scanned (5 hours ago)
Scores higher than 58% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to runhooks/runhooks-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 963 tokens (~53/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 18 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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.10 → 0.1.11 functional
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 48 → 53 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.1.7 → 0.1.10 functional
- Package version: 0.1.7 → 0.1.8 functional
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 5 Nov 2026 · Analysed npm/@runhooks/mcp@0.1.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | runhooks/runhooks-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/runhooks/runhooks-mcp/.github/workflows/publish.yml@refs/tags/v0.1.11 |
| Rekor log index | 3611811927 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:629ce0d2f3c84f22381be1fec6cf451d711002d49f9185769d589971ce0e657c93073d297fc8401f199e1c65b555fdfb66ca3a2a13b75a06364e9a9ad |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
create_alert ~103
Create a failure alert. Fires when a job dead-letters. Channel is email, webhook, or slack.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| consecutiveFailuresThreshold | integer | – | – |
| cooldownMinutes | integer | – | – |
| enabled | boolean | – | – |
| jobId | string|null | – | Scope to one job; omit for all jobs |
| name | string | yes | – |
| target | string | yes | Email address, webhook URL, or Slack webhook URL |
No output schema declared.
No examples provided.
create_job ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| httpConfig | object | yes | – |
| name | string | yes | – |
| retryPolicy | object | – | – |
| schedule | object | yes | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
delete_alert ~20
Delete an alert configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_job ~20
Delete a job permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_alert ~24
Get a single alert configuration by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_job ~23
Get a single job by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_usage ~19
Show the current plan usage and limits for the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_alerts ~15
List your failure-alert configurations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_executions ~50
List recent executions (run history) for a job.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| limit | integer | – | – |
| page | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_jobs ~58
List your scheduled jobs with optional filters and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | – | Filter by name (regex) |
| page | integer | – | – |
| status | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
pause_job ~25
Pause a job — it stops executing until resumed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
provision_account ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional display name for the account |
No output schema declared.
No examples provided.
replay_execution ~23
Re-run a past execution immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| executionId | string | yes | – |
No output schema declared.
No examples provided.
resume_job ~20
Resume a paused job.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
rotate_key ~38
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_alert ~82
Update an alert configuration. Only the fields you provide are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | – |
| consecutiveFailuresThreshold | integer | – | – |
| cooldownMinutes | integer | – | – |
| enabled | boolean | – | – |
| id | string | yes | – |
| jobId | string|null | – | – |
| name | string | – | – |
| target | string | – | – |
No output schema declared.
No examples provided.
update_job ~79
Update an existing job. Only the fields you provide are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| httpConfig | object | – | – |
| id | string | yes | – |
| name | string | – | – |
| retryPolicy | object | – | – |
| schedule | object | – | – |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
whoami ~24
Show the currently authenticated Runhooks account (name, plan, API key prefix).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · @runhooks/mcp
claude mcp add runhooks-runhooks-mcp -- npx -y @runhooks/mcp
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.