net.hookpulse/hookpulse
REMOTE · HOOKPULSE.NET · SCANNED SEP 20
Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1494 tokens (~67/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management46
- Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage90
- 95% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 78% 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 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. See how to fix → Fail
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · hookpulse.net
claude mcp add --transport http net-hookpulse-hookpulse 'https://hookpulse.net/mcp'
{
"mcpServers": {
"net-hookpulse-hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
} {
"servers": {
"net-hookpulse-hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
} [mcp_servers.net-hookpulse-hookpulse] url = "https://hookpulse.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-hookpulse-hookpulse": {
"type": "remote",
"url": "https://hookpulse.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-hookpulse-hookpulse --url 'https://hookpulse.net/mcp' --transport streamable-http
mcp_servers:
net-hookpulse-hookpulse:
url: "https://hookpulse.net/mcp" {
"McpServers": {
"net-hookpulse-hookpulse": {
"Transport": "http",
"Url": "https://hookpulse.net/mcp"
}
}
} assistant mcp add net-hookpulse-hookpulse -t streamable-http -u 'https://hookpulse.net/mcp'
{
"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.
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.
- 20 Sept 26 +1
- Server version: ffd12ea8 → edeb64b6 functional
- 18 Sept 26 +1
- Server version: 9e6f0641 → ffd12ea8 functional
- 17 Sept 26 0
- Server version: 67e71a51 → 9e6f0641 functional
- 16 Sept 26 +1
- Server version: 0e2415e9 → 67e71a51 functional
- 15 Sept 26 0
- Server version: aded9f0b → 0e2415e9 functional
- 14 Sept 26 +1
- Server version: b66641d9 → aded9f0b functional
- New tool “pricing” functional
- 13 Sept 26 +4
- HTTPS: fail → pass ▲ security
- Server version: 7c65b44e → b66641d9 functional
- 12 Sept 26 +1
- Server version: 3caecb8f → 7c65b44e 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 20 Sept 2026 · Probed https://hookpulse.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hookpulse.net | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a382c188b9e84d4a0e405dc0f8462f16 |
| SANs: hookpulse.net, conta.hookpulse.net, *.conta.hookpulse.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hookpulse.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| hookpulse.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hookpulse.net/mcp | Verified | 200 | |
| http (plaintext) | http://hookpulse.net/mcp | HTTPS enforced | 301 | https://hookpulse.net/mcp |
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 →
api_index ~16
Full index of the HookPulse API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
billing ~47
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contact ~230
Support. Agent without captcha → 402 $0.10 x402. After the 1st message: 429 + Retry-After (backoff).
| Name | Type | Req | Description |
|---|---|---|---|
| duracao | string | – | Exposure in days: `30`, `90` or `365`. |
| string | yes | 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 | yes | What you want to say. |
| name | string | yes | 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. |
No output schema declared.
No examples provided.
create_endpoint ~356
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 | yes | 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 |
No output schema declared.
No examples provided.
create_guest ~15
Creates a guest token hp_…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_endpoint ~34
Removes the owner's endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | yes | – |
| id | string | yes | ID of the monitor to deactivate. |
No output schema declared.
No examples provided.
get_endpoint ~55
Status of one endpoint (use the endpoint token if you have it).
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | – |
| id | string | yes | Monitor ID, from `Monitor.id`. |
| token | string | – | endpoint token (query) |
No output schema declared.
No examples provided.
health ~10
Liveness.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
import_crontab ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | string | – | "1" to create the monitors |
| crontab | string | yes | the crontab text |
| guest_token | string | yes | – |
No output schema declared.
No examples provided.
ingest_key ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | – |
No output schema declared.
No examples provided.
ingest_key_rotate ~35
Rotates the ingest key; the previous one stops creating monitors. Existing ones keep working.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | – |
No output schema declared.
No examples provided.
list_endpoints ~25
Lists the guest's/session's endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | yes | – |
No output schema declared.
No examples provided.
list_events ~53
Latest ingest pings.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | – |
| id | string | yes | ID of the monitor. |
| token | string | – | Monitor token, alternative to the `X-Hook-Token` header. |
No output schema declared.
No examples provided.
list_templates ~22
Ingest snippets and the JSON HookPulse POSTs on a miss.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping_ingest ~37
Simulates the cron: GET on /in/:id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
ping_slug ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingestKey | string | yes | Ingest key, from `GET /api/ingest-key`. |
| slug | string | yes | Name of the job; it becomes the monitor name. |
No output schema declared.
No examples provided.
pricing ~17
Current public prices and free allowances; no charge.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
signal_exit_code ~73
The shell exit status: 0 behaves like a ping, 1-255 record the code as a failure.
| Name | Type | Req | Description |
|---|---|---|---|
| exit_code | number | yes | Exit status, 0 to 255. Outside that range it is a 400. |
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
signal_fail ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
signal_start ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
status_feed_rotate ~30
Rotates the status feed token; the previous URL stops working.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | – |
No output schema declared.
No examples provided.
status_feed_url ~33
Public URL (JSON and RSS) with the status of all the owner's endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | – |
No output schema declared.
No examples provided.
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.