# net.hookpulse/hookpulse (remote · hookpulse.net)

Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `hookpulse.net`: 64/100 (this document), [markdown](https://verifymcp.io/servers/net-hookpulse-hookpulse/hookpulse.md), [page](https://verifymcp.io/servers/net-hookpulse-hookpulse/hookpulse)

## Channel facts

- Endpoint: `https://hookpulse.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 22 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1494 tokens (~67/item across 22 items; 22 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 46/100
  - Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 8 additions.
- **Tool Coverage**: 90/100
  - 95% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_endpoint" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the net.hookpulse/hookpulse MCP server?

net.hookpulse/hookpulse is a hosted endpoint at https://hookpulse.net/mcp, so there is nothing to install locally. 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 --transport http net-hookpulse-hookpulse 'https://hookpulse.net/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.net-hookpulse-hookpulse]
url = "https://hookpulse.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-hookpulse-hookpulse": {
      "type": "remote",
      "url": "https://hookpulse.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-hookpulse-hookpulse --url 'https://hookpulse.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-hookpulse-hookpulse:
    url: "https://hookpulse.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-hookpulse-hookpulse": {
      "Transport": "http",
      "Url": "https://hookpulse.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-hookpulse-hookpulse -t streamable-http -u 'https://hookpulse.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-hookpulse-hookpulse": {
      "type": "http",
      "url": "https://hookpulse.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-20 (score 64, +1)

- [functional] Server version: ffd12ea8 → edeb64b6

### 2026-09-18 (score 63, +1)

- [functional] Server version: 9e6f0641 → ffd12ea8

### 2026-09-17 (score 62, 0)

- [functional] Server version: 67e71a51 → 9e6f0641

### 2026-09-16 (score 62, +1)

- [functional] Server version: 0e2415e9 → 67e71a51

### 2026-09-15 (score 61, 0)

- [functional] Server version: aded9f0b → 0e2415e9

### 2026-09-14 (score 61, +1)

- [functional] Server version: b66641d9 → aded9f0b
- [functional] New tool “pricing”

### 2026-09-13 (score 60, +4)

- [security improvement] HTTPS: fail → pass
- [functional] Server version: 7c65b44e → b66641d9

### 2026-09-12 (score 56, +1)

- [functional] Server version: 3caecb8f → 7c65b44e

## MCP tools (22)

### `api_index` (~16 tokens)

Full index of the HookPulse API.

### `health` (~10 tokens)

Liveness.

### `create_guest` (~15 tokens)

Creates a guest token hp_…

### `list_endpoints` (~25 tokens)

Lists the guest's/session's endpoints.

Input parameters:

- `guest_token` (string, required)

### `create_endpoint` (~356 tokens)

Creates a dead-man endpoint. Use cron+tz+grace_sec for a real schedule (mutually exclusive with interval_sec) or interval_sec for plain silence detection. max_duration_sec alerts when a run opened by /in/:id/start hangs. May return 402 x402 when it leaves the free tier.

Input parameters:

- `alert_repeat_sec` (number): gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default
- `alert_to` (string): E-mail to alert on a miss; without it, the account is alerted.
- `alert_url` (string): Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n).
- `cron` (string): five-field cron, e.g. 0 3 * * *
- `grace_sec` (number): tolerance after the scheduled time, default 90, min 30
- `guest_token` (string, required)
- `interval_sec` (number): Tolerated silence, in seconds. Below the free minimum, it costs.
- `max_duration_sec` (number): ceiling for an open run in seconds, 60..86400; null or 0 turns it off
- `name` (string, required): how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected
- `paused_until` (string): maintenance window end (UTC ISO), max 30 days ahead
- `tags` (array): up to 8 tags to group the monitor; lower-cased, [a-z0-9._-], max 32 chars each
- `tz` (string): IANA time zone for cron, default UTC

### `import_crontab` (~85 tokens)

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.

Input parameters:

- `apply` (string): "1" to create the monitors
- `crontab` (string, required): the crontab text
- `guest_token` (string, required)

### `get_endpoint` (~55 tokens)

Status of one endpoint (use the endpoint token if you have it).

Input parameters:

- `guest_token` (string)
- `id` (string, required): Monitor ID, from `Monitor.id`.
- `token` (string): endpoint token (query)

### `delete_endpoint` (~34 tokens)

Removes the owner's endpoint.

Input parameters:

- `guest_token` (string, required)
- `id` (string, required): ID of the monitor to deactivate.

### `list_events` (~53 tokens)

Latest ingest pings.

Input parameters:

- `guest_token` (string)
- `id` (string, required): ID of the monitor.
- `token` (string): Monitor token, alternative to the `X-Hook-Token` header.

### `ping_ingest` (~37 tokens)

Simulates the cron: GET on /in/:id.

Input parameters:

- `id` (string, required): Monitor ID, from `Monitor.ingest_url`.

### `signal_start` (~56 tokens)

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.

Input parameters:

- `id` (string, required): Monitor ID, from `Monitor.ingest_url`.

### `signal_fail` (~61 tokens)

Says the run FAILED. The ingest never sends e-mail: the 5-minute cron turns it into an alert with reason `fail`, under the same one-per-24h cap.

Input parameters:

- `id` (string, required): Monitor ID, from `Monitor.ingest_url`.

### `signal_exit_code` (~73 tokens)

The shell exit status: 0 behaves like a ping, 1-255 record the code as a failure.

Input parameters:

- `exit_code` (number, required): Exit status, 0 to 255. Outside that range it is a 400.
- `id` (string, required): Monitor ID, from `Monitor.ingest_url`.

### `ingest_key` (~57 tokens)

Returns (minting the first time) the key for /in/<key>/<slug>, where a ping creates its own monitor inside the free tier. Instruments a whole fleet with no setup call per job.

Input parameters:

- `guest_token` (string)

### `ingest_key_rotate` (~35 tokens)

Rotates the ingest key; the previous one stops creating monitors. Existing ones keep working.

Input parameters:

- `guest_token` (string)

### `ping_slug` (~78 tokens)

Ping that creates its own monitor on the first hit. Same slug = same monitor; 402 when the free tier is full, and then nothing is written.

Input parameters:

- `ingestKey` (string, required): Ingest key, from `GET /api/ingest-key`.
- `slug` (string, required): Name of the job; it becomes the monitor name.

### `billing` (~47 tokens)

Free plan, x402 prices and the trial offer: sign-up with a confirmed e-mail = 90 days without the usage paywall (`trial` field; with a session it shows the state).

### `status_feed_url` (~33 tokens)

Public URL (JSON and RSS) with the status of all the owner's endpoints.

Input parameters:

- `guest_token` (string)

### `status_feed_rotate` (~30 tokens)

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

Input parameters:

- `guest_token` (string)

### `list_templates` (~22 tokens)

Ingest snippets and the JSON HookPulse POSTs on a miss.

### `contact` (~230 tokens)

Support. Agent without captcha → 402 $0.10 x402. After the 1st message: 429 + Retry-After (backoff).

Input parameters:

- `duracao` (string): Exposure in days: `30`, `90` or `365`.
- `email` (string, required): Where to reply.
- `empresa` (string): Who is proposing, when it is a company.
- `espaco` (array): Placement ids from `GET /api/partners`, up to 6.
- `message` (string, required): What you want to say.
- `name` (string, required): What to call the person writing.
- `orcamento` (string): `ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`.
- `pagamento` (string): `usdc`, `deposito` or `a_combinar`.
- `site` (string): Website of who is proposing.
- `tipo` (string): Proposal: `patrocinio`, `parceria` or `anuncio`. Turns on the fields below.

### `pricing` (~17 tokens)

Current public prices and free allowances; no charge.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-hookpulse-hookpulse/hookpulse#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 61
- 2026-09-14: 61
- 2026-09-13: 60
- 2026-09-12: 56
- 2026-09-11: 55
- 2026-09-10: 55
- 2026-09-09: 54
- 2026-09-08: 54
- 2026-09-07: 52
- 2026-09-06: 48
- 2026-09-05: 51

## Common questions

### What is the net.hookpulse/hookpulse MCP server?

net.hookpulse/hookpulse is an MCP server listed in the public MCP registry as net.hookpulse/hookpulse. Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed. This page covers its hosted endpoint (https://hookpulse.net/mcp).

### Is the net.hookpulse/hookpulse MCP server safe to use?

net.hookpulse/hookpulse scores 64 out of 100 on VerifyMCP. 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 net.hookpulse/hookpulse MCP server expose?

net.hookpulse/hookpulse exposes 22 tools: api_index, health, create_guest, list_endpoints, create_endpoint, and 17 more. Their descriptions and schemas cost roughly 1,425 tokens of context every time the server is loaded.

### Does the net.hookpulse/hookpulse MCP server require authentication?

No. We connected to net.hookpulse/hookpulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the net.hookpulse/hookpulse MCP server still maintained?

net.hookpulse/hookpulse is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://hookpulse.net/mcp
- Website: https://hookpulse.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-hookpulse-hookpulse/hookpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-hookpulse-hookpulse/hookpulse.json
- HTML version of this page: https://verifymcp.io/servers/net-hookpulse-hookpulse/hookpulse