HookPulse MCP server
Commit Nov 7, 2026Monitor cron jobs, webhooks, backups, and GitHub Actions workflows to receive alerts when routines fail or stop running.
Also known as wrpbr/hookpulse
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Nov 7, 2026
- License
- MIT-0
What is HookPulse MCP?
HookPulse monitors cron jobs, webhooks, backups, and GitHub Actions workflows to receive alerts when routines fail or stop running.
Summary generated from the project's README
About HookPulse MCP server
Monitoring cron jobs, webhooks, backups, and GitHub Actions workflows for failures is what HookPulse enables for developers using AI agents. It tracks scheduled routines via check-in links and sends alerts through email or webhooks like Slack and Discord if a task stops running or reports an error. This service is accessible to agents like Claude Code, Codex, and Cursor through a remote MCP server that requires no local installation or API keys to start.
Users can manage their monitoring setup by creating individual monitors with specific intervals, time zones, and allowed delays. The system supports importing entire crontabs to propose new monitors or using a single setup key to instrument a fleet of routines. For GitHub Actions, it can monitor scheduled workflows using a dedicated action or a GitHub App that opens repository issues when runs fail. While the first ten monitors and check-ins are free, additional email alerts require a one-time credit purchase via the website.
What you can do with it
- 1Import existing crontab schedulesAsk your agent to convert a text-based crontab into a set of proposed monitors.
- 2Create specific time-based monitorsInstruct an AI to set up a new monitor for a backup routine with a specific time zone and schedule.
- 3Monitor GitHub Actions workflowsSet up automated monitoring for scheduled GitHub workflows to receive alerts if they fail.
- 4Check current routine statusRequest a summary of all active monitors and their most recent check-in results.
Written from the project's README. Every use case is checked against a quote from it.
How to install HookPulse MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall HookPulse MCP in Claude Code
$ claude mcp add --transport http hookpulse https://hookpulse.net/mcpInstall HookPulse MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}Install HookPulse MCP in VS Code
.vscode/mcp.json
{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Install HookPulse MCP in VS Code CLI
$ code --add-mcp '{"name":"hookpulse","type":"http","url":"https://hookpulse.net/mcp"}'Install HookPulse MCP in Codex
$ codex mcp add hookpulse --url https://hookpulse.net/mcpInstall HookPulse MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.hookpulse] url = "https://hookpulse.net/mcp"
Install HookPulse MCP in Gemini CLI
$ gemini mcp add -s user --transport http hookpulse https://hookpulse.net/mcpInstall HookPulse MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablewrpbr/hookpulse is public and reachablegithub.com/wrpbr/hookpulse ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MIT-0spdx.org/licenses/MIT-0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-10github.com/wrpbr/hookpulse ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 592 msPass
README
View on GitHubHookPulse — skill and MCP server for AI agents
HookPulse tells you when a cron job, webhook, backup or scheduled GitHub Actions workflow stops running. Each routine gets a check-in link. If the check-in does not arrive by the expected time, or the routine reports a failure, HookPulse sends an alert by e-mail or to a webhook such as Slack or Discord, and it tells you when the routine comes back. This repository packages the HookPulse skill and the connection to its remote MCP server for Claude Code, Codex, Cursor and other agents.
Site: https://hookpulse.net · MCP server: https://hookpulse.net/mcp?checkout=site ·
Prices: https://hookpulse.net/pricing · API docs: https://hookpulse.net/developers
What your agent can do
- Create a monitor for a routine, with an interval or a cron schedule, a time zone and an allowed delay.
- Import a crontab: see the proposed monitors first, then create them in one call.
- Give each run a start, a success or a failure signal, with the shell exit code.
- Instrument a whole fleet with one setup key: the first check-in of each name creates its monitor.
- Read the state of every monitor, the latest check-ins and the public status page.
Try: "Import my crontab into HookPulse and show me what it would create." or "Create a monitor for the nightly backup that runs at 03:00 São Paulo time."
GitHub Actions
A scheduled workflow gets a monitor with one step and no secret. The job's identity token tells HookPulse which repository and workflow it is; the first run creates the monitor with the workflow's schedule:
permissions:
contents: read
id-token: write
jobs:
backup:
runs-on: ubuntu-latest
steps:
- run: ./backup.sh
- uses: wrpbr/hookpulse-action@v1
if: always()
with:
status: ${{ job.status }}
See wrpbr/hookpulse-action for alerts and options. Without changing any workflow, install the HookPulse GitHub App: a missed or failed scheduled run opens an issue in the repository, and the next good run closes it.
Install
Claude Code, as a plugin with the skill and the MCP server:
/plugin marketplace add wrpbr/hookpulse
/plugin install hookpulse@hookpulse
Any agent that reads Agent Skills (Claude Code, Codex, Cursor, OpenCode and others):
npx skills add wrpbr/hookpulse
Only the MCP server (remote, Streamable HTTP, no key needed to start):
claude mcp add --transport http hookpulse 'https://hookpulse.net/mcp?checkout=site' # Claude Code
codex mcp add hookpulse --url 'https://hookpulse.net/mcp?checkout=site' # Codex
{ "mcpServers": { "hookpulse": { "url": "https://hookpulse.net/mcp?checkout=site" } } }
The JSON above goes in .cursor/mcp.json for Cursor and in the MCP settings of most other clients. The GitHub
Copilot coding agent takes it in the repository settings, under Copilot → MCP servers, with "type": "http" and
the tools you allow.
Price
Ten monitors are free, and check-ins have no charge. E-mail alerts on one monitor are free; e-mail alerts on each
additional monitor cost a one-time fee. Alerts to webhooks have no alert charge. You buy credit on the site, and
nothing renews automatically. The plugin never pays: with checkout=site, the MCP server has no purchase tool and
no payment argument. The current prices are at https://hookpulse.net/pricing.
What the plugin sends
The skill tells the agent to call the HookPulse API at hookpulse.net. The MCP server also runs at hookpulse.net. The names, schedules and alert destinations of your monitors go to hookpulse.net over HTTPS. The plugin runs no local program and reads no local file; the crontab import reads only the text you paste.
Em português
O HookPulse avisa quando uma rotina agendada, um webhook, um backup ou um workflow agendado do GitHub Actions para de rodar. Cada rotina ganha um link de check-in; se ele não chega no horário, ou se a rotina avisa uma falha, o alerta sai por e-mail ou por webhook. Este repositório traz a skill e a conexão com o servidor MCP remoto. Instale com os comandos acima. Dez monitores são grátis. Os preços estão em https://hookpulse.net/pricing.
Files
| File | What it is |
|---|---|
skills/hookpulse/SKILL.md |
The skill: which tool answers which question, and the rules for alerts and limits |
.mcp.json |
The remote MCP server of the plugin |
.claude-plugin/plugin.json |
The plugin manifest |
.claude-plugin/marketplace.json |
Lets Claude Code add this repository as a plugin marketplace |
server.json |
The manifest in the official MCP registry (net.hookpulse/hookpulse) |
glama.json |
The maintainer for the Glama MCP directory |
License and contact
The files in this repository are under the MIT-0 license. The HookPulse service is not part of this license: its use follows the terms of use and the privacy policy. For questions or problems, open an issue here or write to contato@hookpulse.net.
HookPulse MCP questions
How do I add HookPulse MCP to Claude Code?
Run claude mcp add --transport http hookpulse https://hookpulse.net/mcp in your terminal. Add --scope user to make it available in every project.
How do I add HookPulse MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How much does HookPulse cost?
Ten monitors and check-ins are free. Email alerts on one monitor are free, while additional email alerts require a one-time fee. Webhook alerts have no charge.
Does the MCP server require an API key to start?
No, the remote MCP server is streamable via HTTP and does not require a key to start.