# @runhooks/mcp

Model Context Protocol server for Runhooks — let AI agents schedule and manage HTTP webhooks

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.1.7
- **Author:** io.github.runhooks
- **License:** MIT
- **npm:** @runhooks/mcp
- **Source:** https://github.com/runhooks/runhooks-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-15T07:22:21.588Z
- **Version scanned:** 0.1.7
- **CVEs:** none found by OSV at scan time

## Tools

18 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `provision_account` — Create a new anonymous Runhooks account (no email required) and return an API key. Save the returned apiKey and set it as RUNHOOKS_API_KEY to use every other to
- `whoami` — Show the currently authenticated Runhooks account (name, plan, API key prefix).
- `rotate_key` — Rotate the API key. The old key stops working immediately; the new key is returned.
- `create_job`
- `list_jobs` — List your scheduled jobs with optional filters and pagination.
- `get_job` — Get a single job by its ID.
- `update_job` — Update an existing job. Only the fields you provide are changed.
- `delete_job` — Delete a job permanently.
- `pause_job` — Pause a job — it stops executing until resumed.
- `resume_job` — Resume a paused job.
- `list_executions` — List recent executions (run history) for a job.
- `replay_execution` — Re-run a past execution immediately.
- `get_usage` — Show the current plan usage and limits for the account.
- `list_alerts` — List your failure-alert configurations.
- `create_alert` — Create a failure alert. Fires when a job dead-letters. Channel is email, webhook, or slack.
- `get_alert` — Get a single alert configuration by its ID.
- `update_alert` — Update an alert configuration. Only the fields you provide are changed.
- `delete_alert` — Delete an alert configuration.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@runhooks/mcp\"\n      ],\n      \"env\": {\n        \"RUNHOOKS_API_KEY\": \"<YOUR_RUNHOOKS_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `RUNHOOKS_API_KEY` — Runhooks API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 53, ceiling 53 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40runhooks%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40runhooks%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40runhooks%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40runhooks%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.