原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Hookpulse

作者:wrpbr版本 1.1.0i★ 0i在云端运行
注册名称net.hookpulse/hookpulse

安装方法

What it does

Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.

  • Connects 在云端运行
  • Account or key No key needed
  • Category 其他

安装

选择你使用的 AI 应用,然后复制设置。

通过 4/4 项检查 · 你的提问会经过开发者的服务器(hookpulse.net) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Hookpulse
    Remote MCP server URL · 地址https://hookpulse.net/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsHookpulse

  4. 试一试

    用 Hookpulse 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Hookpulse,或回答中出现 Hookpulse 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Hookpulse
    Connection · 地址https://hookpulse.net/mcp
  3. 在聊天中选择 Hookpulse

    开启新聊天,输入前先从插件列表中选择 Hookpulse

  4. 试一试

    用 Hookpulse 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Hookpulse,或回答中出现 Hookpulse 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user hookpulse https://hookpulse.net/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Hookpulse 在列表中并显示已连接

  4. 试一试

    用 Hookpulse 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Hookpulse,或回答中出现 Hookpulse 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Hookpulse 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Hookpulse,或回答中出现 Hookpulse 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Hookpulse 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Hookpulse,或回答中出现 Hookpulse 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://hookpulse.net/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Hookpulse 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user hookpulse https://hookpulse.net/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "hookpulse": {
      "url": "https://hookpulse.net/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "hookpulse": {
      "type": "http",
      "url": "https://hookpulse.net/mcp"
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ hookpulse.net
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.1.0
分类i
其他
发布到注册中心i
2026年11月10日
代码最后更新i
2026年11月7日
作者
wrpbr
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月13日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • list_plans

    The plans for sale, with price and term, and the account's active plan. Each purchase lasts 30 days, with no automatic renewal. Each purchase lasts 30 days, with no automatic renewal. Without an account or wallet credential, `account` is `null`.

  • buy_plan

    Buy a plan: starter (40 more monitors, up to 50), team (90 more monitors, up to 100), business (490 more monitors, up to 500). Each purchase lasts 30 days, with no automatic renewal. Answers 402 with the price; pay with x402 or prepaid credit and repeat. Each purchase lasts 30 da

  • cancel_plan

    Cancel the active plan. Nothing else is charged; a purchase under 7 days and a paid period that has not started are refunded and end now, and the rest of the paid period stays active until keeps_until. Requires accept_data_removal: true. Send `{ "accept_data_removal": true }`. Th

  • api_index

    Full index of the HookPulse API.

  • health

    Read service liveness before using HookPulse. Returns the health response; does not check a monitor.

  • create_guest

    Creates a guest token hp_… Keep the token: without it there is no way back to the monitors, unless you have already tied them to an e-mail.

  • list_endpoints

    Lists the guest's/session's endpoints.

  • create_endpoint

    Create a monitor for a routine. Use cron, tz and grace_sec for a schedule, or interval_sec for a fixed check-in interval. Set max_duration_sec to detect an open run that exceeds its time limit. Without an owner token, creation returns guest_token; keep it private for later calls.

  • create_site

    Monitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Without an owner token, creation returns guest_token; keep it private. Read billing before a paid option. A charged request returns HTTP 402. We keep th

  • check_site

    Check a site monitor now. One call every 10 seconds per destination host. One call every 10 seconds per destination host, for everyone: the button cannot hammer a site. The first state of a new site comes from here, without an alert — you are looking at it. After that, the state

  • list_sites

    The state of every site you monitor (up, down, waiting, paused), with the last check. The same answer is the snapshot of the live subscription (`/api/realtime/`): after it, every check arrives as an event, so a screen never has to poll.

  • import_crontab

    Reads a crontab and proposes one monitor per scheduled line. Without apply=1 nothing is written; the proposal says what was ignored and why. Passwords in the command are redacted. The body is the crontab itself, as `text/plain`. Without `?apply=1` **nothing is written**: you get

  • get_endpoint

    Status of one endpoint (use the endpoint token if you have it). The monitor token only reads: it lets you put the state on a third-party dashboard without handing over the owner's credential. With a schedule it is here that `next_expected_at` says when the next run is due. Only t

  • delete_endpoint

    Removes the owner's endpoint.

  • list_events

    Latest ingest pings.

  • ping_ingest

    Simulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret. It costs nothing and there is no quota per ping.

  • signal_start

    Says the run STARTED. Does not clear the dead-man clock: a routine that starts and hangs still becomes a miss. The next success records the duration. `start` is not proof of life: it does not move `last_event_at` and does not clear the miss counter, so a routine that starts and h

  • signal_fail

    Record a failed run. The next five-minute check sends the alert with reason fail. The monitor's alert_repeat_sec controls repeated alerts; the default is 24 hours. Failing is not proof of life either: the clock keeps running. The ingest never sends e-mail and never calls out — it

  • signal_exit_code

    The shell exit status: 0 behaves like a ping, 1-255 record the code as a failure. `curl -fsS $ORIGIN/in/ID/$?` at the end of a script is the whole integration. `0` behaves exactly like a plain ping; 1 to 255 record the code and leave the failure for the cron.

  • ingest_key

    Returns (minting the first time) the key for /in/ / , where a ping creates its own monitor inside the free tier. Instruments a whole fleet with no setup call per job. One key per owner. Point a whole fleet at `/in/ / ` and each job creates its monitor on the first check-in, **ins

  • ingest_key_rotate

    Rotates the ingest key; the previous one stops creating monitors. Existing ones keep working. Monitors already created keep working — rotating only revokes the power to create new ones.

  • ping_slug

    Create a monitor on its first check-in. The same slug uses the same monitor. Service and billing limits apply. A rejected creation writes no monitor or event. The slug becomes the monitor name and its identity: the same slug always means the same monitor, so a retry never creates

  • signal_slug

    Send start, fail or an exit code by name, with the ingest key; the first signal of a new name creates its monitor. The same signals as `/in/:id/start`, `/in/:id/fail` and `/in/:id/:exit_code`, for a fleet that only knows the ingest key: the job sends its name, not the monitor id.

  • pricing

    Read current free allowances, options with billing off, prices and the account's 7-day trial. E-mail alerts cost $0.10 once per additional monitor, even with a reused address. Check before creating the second monitor or lowering the interval: it is the number IN FORCE, not the do

  • status_feed_url

    Public URL (JSON and RSS) with the status of all the owner's endpoints. The feed token only reads status: it does not create, change or delete. Whoever has the link sees the dashboard — treat it as a secret.

  • status_feed_rotate

    Rotates the status feed token; the previous URL stops working.

  • list_templates

    Ingest snippets and the JSON HookPulse POSTs on a miss. It exists so nobody guesses the alert format: `miss_json` and `recovery_json` here are the same bodies that arrive at your `alert_url`. Slack and Discord receive only the field they read.

  • contact

    Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. Free, no captcha and no payment; one message every 10 s per network (one that arrives sooner waits its turn). One route for a question and for a sponsorship, partnership or ad p

  • get_api_x402_check

    Checks a URL once for an agent, paid per call: status, response time, keyword and TLS certificate, with no account and no monitor. One reading with the probe of the site monitors, and the certificate of an https address that answered. A request without payment gets the 402 with t

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月15日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 hookpulse.net 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于8天前

  • – 不适用

    有许可证

    不适用:由 hookpulse.net 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✓ 通过

    端点有响应

    在 755 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 29 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 19878 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 19878 个服务器的 90% 更新
  • 基础检查结果等于或优于此分类中其他 19878 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Hookpulse 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于8天前,最新版本(1.1.0)于5天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

作者:koala73广泛使用★ 9.1万昨天更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92652个月前更新

在云端运行✓ 服务方 · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

作者:JanDeDobbeleer广泛使用★ 2.4万 整个仓库的星标26天前更新

在云端运行✓ 服务方 · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582814个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51354个月前更新

在云端运行✓ 服务方 · jitsu.com
  • World Monitor — 在云端运行,无需安装 · 不需要密钥
  • openstatus — 在云端运行,无需安装 · 不需要密钥
  • Oh My Posh Validator — 在云端运行,无需安装 · 不需要密钥
  • Strata — 在云端运行,无需安装 · 不需要密钥
  • Jitsu — 在云端运行,无需安装 · 不需要密钥

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

HookPulse — 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

FileWhat it is
skills/hookpulse/SKILL.mdThe skill: which tool answers which question, and the rules for alerts and limits
.mcp.jsonThe remote MCP server of the plugin
.claude-plugin/plugin.jsonThe plugin manifest
.claude-plugin/marketplace.jsonLets Claude Code add this repository as a plugin marketplace
server.jsonThe manifest in the official MCP registry (net.hookpulse/hookpulse)
glama.jsonThe 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.