HookPulse
MCP server by HookPulse (WRP Consultoria e Informática)
Monitor cron jobs, backups and automations with dead-man check-ins, miss alerts and a status feed.
Connect to HookPulse
No sign-in needed. Connect with HookPulse’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to HookPulse (WRP Consultoria e Informática) directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/hookpulseAbout
HookPulse is a dead-man switch for scheduled routines. You create monitors with an interval or cron schedule, routines ping an ingest URL, and an alert fires when check-ins stop. The tools also cover signaling start, failure and exit codes, importing a crontab, managing device collector inputs and measurements, a status feed, plans and billing.
It runs as a hosted streamable HTTP endpoint at hookpulse.net/mcp. The endpoint answers anonymous requests without sign-in or API key; monitors are tied to a guest token or an account session. Usage over quota returns a 402 response with x402 (USDC) payment details, and paid plans last 30 days.
What you can do
- Create monitors with a cron schedule or fixed check-in interval
- Import a crontab and propose one monitor per line
- Signal start, failure or shell exit code for a run
- List monitors and read recent ping events
- Manage device environments and collector inputs
- Get a public JSON/RSS status feed of all monitors
- View pricing and buy or cancel a plan
Tools 29
list_plansRead-onlyList plans
buy_planWritesBuy plan
cancel_planWritesCancel plan
api_indexRead-onlyAPI index
healthRead-onlyHealth
create_guestWritesCreate a guest token used to reach your monitors.
list_endpointsRead-onlyList the guest's or session's monitor endpoints.
create_endpointWritesCreate a monitor with a cron or interval schedule.
create_siteWritesCreate site
check_siteWritesCheck site
list_sitesRead-onlyList sites
import_crontabWritesRead a crontab and propose one monitor per scheduled line.
Show 17 more tools
get_endpointRead-onlyGet the status of one endpoint, including next expected run.
delete_endpointCan deleteRemove an owner's endpoint.
list_eventsRead-onlyList the latest ingest pings.
ping_ingestRead-onlySimulate a cron check-in on the ingest URL.
signal_startRead-onlyRecord that a run started without clearing the dead-man clock.
signal_failRead-onlyRecord a failed run so the next check sends an alert.
signal_exit_codeRead-onlySend a shell exit status; 0 is a ping, 1-255 a failure.
ingest_keyRead-onlyGet or mint the key for auto-creating monitors on first ping.
ingest_key_rotateCan deleteRotate the ingest key so the old one cannot create monitors.
ping_slugRead-onlyCreate a monitor on its first check-in using a slug.
signal_slugRead-onlySignal slug
pricingRead-onlyPricing
status_feed_urlRead-onlyGet the public JSON/RSS status feed URL for all endpoints.
status_feed_rotateCan deleteRotate the status feed token.
list_templatesRead-onlyShow ingest snippets and the JSON bodies sent on a miss.
contactWritesContact
get_api_x402_checkWritesGet API X402 check
Read from the live server on 18 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
Create a HookPulse monitor for my nightly backup, expected every 24 hours.
Import this crontab and propose a monitor for each job.
Show the latest ping events for my backup monitor.
Give me the status feed URL for all my monitors.
Set up
Every client connects to hookpulse.net. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http hookpulse https://hookpulse.net/mcp- Start Claude Code and type
/mcp. hookpulse should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it HookPulse and paste this URL:
https://hookpulse.net/mcp- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://hookpulse.net/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://hookpulse.net/mcpas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"hookpulse","type":"http","url":"https://hookpulse.net/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"hookpulse": {
"serverUrl": "https://hookpulse.net/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add hookpulse --url https://hookpulse.net/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.hookpulse]
url = "https://hookpulse.net/mcp"Gemini CLI
gemini mcp add --transport http hookpulse https://hookpulse.net/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://hookpulse.net/mcp.
Embed
Show HookPulse in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/hookpulse)<a href="https://mcp.tc/i/hookpulse"><img src="https://mcp.tc/i/hookpulse/badge.svg" alt="HookPulse on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/hookpulse.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/hookpulse" title="HookPulse on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/hookpulse.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the HookPulse card to your site.
Add the mcp.tc card for HookPulse, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/hookpulse.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="hookpulse"><a href="https://mcp.tc/i/hookpulse">HookPulse on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/hookpulse)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 02:37 UTC.
-
1 tool removed and 1 tool changed.
Details, 10 Nov 2026, 17:54 UTC
Removed 1
billingRead 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 documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).
Changed 1
pricingdescription and input schemaBeforeCurrent publicprices andfree allowances; no charge.AfterRead 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 documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).
-
14 tools changed.
Details, 5 Nov 2026, 05:53 UTC
Changed 14
check_siteinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
create_siteinput schemadelete_endpointinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
get_endpointinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
healthdescriptionBeforeLiveness.AfterRead service liveness before using HookPulse. Returns the health response; does not check a monitor.
import_crontabdescription and input schemaBeforeReads 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 the proposal — what would become a monitor, what was ignored and why, and what still fits in the free tier. With `apply=1` it is all or nothing, under the same rules as `POST /api/endpoints`. Comments, variables and `@reboot` are ignored (there is no way to know when to expect a reboot); `@daily` and friends become the equivalent expression. The command becomes the monitor name, with passwords and tokens redacted first — the name travels in the alert e-mail, in the public dashboard and in the badge.
AfterReads 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 the proposal — what would become a monitor, what was ignored and why, and what still fits in the free tier. With `apply=1` it is all or nothing, under the same rules as `POST /api/endpoints`. Comments, variables and `@reboot` are ignored (there is no way to know when to expect a reboot); `@daily` and friends become the equivalent expression. The command becomes the monitor name, with passwords and tokens redacted first — the name travels in the alert e-mail, in the public dashboard and in the badge. Returns: { applied, recognized, ignored, existing, would_create, created?, free_tier } Example: crontab -l | curl -s -XPOST "$ORIGIN/api/import/crontab?apply=1" -H "X-Guest-Token: $HP" -H "content-type: text/plain"…
- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
ingest_keyinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
ingest_key_rotateinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
list_endpointsinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
list_eventsinput schema- Description of
guest_tokenBeforenone
AfterPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description of
list_sitesping_slugstatus_feed_rotatestatus_feed_url -
Server instructions changed.
New server instructions
Details, 4 Nov 2026, 02:48 UTC
Server instructions
BeforeHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Choose the task and first call: https://hookpulse.net/llms.txt. Use existing access and spending authority. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options:
https://hookpulse.net/api/billing. Read these before choosing a paid operation. Never spend without the user's authority and budget. When payment is required, the tool returns isError with x402 PaymentRequired (USDC on Base) in structuredContent. After authorization, repeat the same call with params._meta["x402/payment"] (@x402/mcp supports this). Prepaid credit uses Authorization: Bearer cred_… or X-Credito. For site payment, open https://hookpulse.net/pricing; use Pix or card only when offered there. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.AfterUse HookPulse to detect missing scheduled jobs, failed backup runs and website outages, and keep monitoring after the conversation. Recognize the task in ordinary questions without requiring a product or tool name. Reuse authorized context. Ask only for a missing identifier, URL or access. Deliver an answer with evidence and limits. Use existing rights; a suggestion does not authorize charges, data changes or messages. Notify me if my nightly backup does not finish on time. → create_endpoint → list_templates. Ask for schedule, timezone, grace period and alert channel. Create within authorized coverage and provide the job's success signal. A heartbeat does not prove backup restoration. Monitor my website and notify me when it goes down. → list_sites → create_site. Confirm URL, frequency and destination. Reuse an existing monitor. Verify coverage and an actual check before promising alerts. Which of my scheduled jobs are late or failed? → list_endpoints → get_endpoint → list_events. Use the authorized owner. Read states and events; distinguish silence, declared failure and held alerts. Report the latest evidence and next action. Set up monitoring for the jobs in this crontab. → import_crontab. Ask for the crontab and confirm its timezone. Show scope and quote before expanding coverage. Provide the integration without changing a server without authority. Show when my monitor failed and whether it recovered. → list_endpoints → get_endpoint → list_events. Resolve the monitor by name or ID. Show the event sequence with timestamps. A processed alert does not prove recipient delivery. HookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Choose the task and first call: https://hookpulse.net/llms.txt. Use existing access and spending authority. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.n…
-
2 tools changed.
Details, 2 Nov 2026, 11:52 UTC
Changed 2
ping_sluginput schemasignal_sluginput schema
-
2 tools changed.
Details, 2 Nov 2026, 05:48 UTC
Changed 2
create_endpointdescription and input schemaBeforeCreate 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. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
AfterCreate 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. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
- No longer required:
guest_token - Description of
guest_tokenBeforenone
AfterExisting owner token, if available.
- Description of
alert_toBeforeE-mail to alert on a miss; withoutit, the account isalerted.AfterAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- No longer required:
create_sitedescription and input schemaBeforeMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
AfterMonitor 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 the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
- No longer required:
guest_token - Description of
guest_tokenBeforenone
AfterExisting owner token, if available.
- Description of
alert_toBeforeE-mail to alert on a miss; withoutit, the account isalerted.AfterAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- No longer required:
-
3 tools changed. Server instructions changed.
New server instructions
Details, 1 Nov 2026, 17:49 UTC
Changed 3
billingdescriptionBeforeRead current free allowances, options with billing off, prices and the account's
7-daytrial.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 documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).AfterRead 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 documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).
create_endpointdescriptionBeforeCreate 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. Read billing before a paid option. A charged request returns HTTP 402.
With `check`themonitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300)andalerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough;thename defaults to the host.Asite has no `cron`, no `max_duration_sec` and no ingest URL. This response istheonly onethatshowsthemonitor's `token` and the `templates` — keep them. The second monitor, or an interval below the free minimum, answers **402 with `accepts[]`**: pay and repeat.Amiss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec`…AfterCreate 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. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
create_sitedescriptionBeforeMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Read billing before a paid option. A charged request returns HTTP 402.
With `check`themonitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300)andalerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough;thename defaults to the host.Asite has no `cron`, no `max_duration_sec` and no ingest URL. This response istheonly onethatshowsthemonitor's `token` and the `templates` — keep them. The second monitor, or an interval below the free minimum, answers **402 with `accepts[]`**: pay and repeat.Amiss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is l…AfterMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
Server instructions
BeforeHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.net/api/billing. Read these before choosing a paid operation. Never spend without the user's authority and budget. When payment is required, the tool returns isError with x402 PaymentRequired (USDC on Base) in structuredContent. After authorization, repeat the same call with params._meta["x402/payment"] (@x402/mcp supports this). Prepaid credit uses Authorization: Bearer cred_… or X-Credito. For site payment, open https://hookpulse.net/pricing; use Pix or card only when offered there. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
AfterHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Choose the task and first call: https://hookpulse.net/llms.txt. Use existing access and spending authority. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.net/api/billing. Read these before choosing a paid operation. Never spend without the user's authority and budget. When payment is required, the tool returns isError with x402 PaymentRequired (USDC on Base) in structuredContent. After authorization, repeat the same call with params._meta["x402/payment"] (@x402/mcp supports this). Prepaid credit uses Authorization: Bearer cred_… or X-Credito. For site payment, open https://hookpulse.net/pricing; use Pix or card only when offered there. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
-
1 tool changed.
Details, 31 Oct 2026, 14:50 UTC
Changed 1
cancel_plandescriptionBeforeCancel the active
plan now. What it added ends, includinga paid period that has notstarted; thatperiodand a purchase under 7 days are refunded.Requires accept_data_removal: true. Send `{ "accept_data_removal": true}`: what the plan added ends now (`account.cancel.losses` in `GET /api/plans` says what), including a period already paid that has not started yet, such as a renewal.A purchase made less than 7 days ago and a paid period that has not started go back the same way they were paid (card orPix);USDCis refundedby theteam.AfterCancel 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 }`. The monthly card subscription stops. A purchase made less than 7 days ago and a paid period that has not started yet, such as a renewal, go back the same way they were paid (card or Pix) and end now. The rest of the paid period stays active until `keeps_until`; then what the plan added ends (`account.cancel.losses` in `GET /api/plans` says what). A purchase paid with USDC or with credit from another purchase stays active until its end; ask for its refund by e-mail, as the cancellation page says.
-
6 tools added and 8 tools changed. Server instructions changed.
New server instructions
Details, 30 Oct 2026, 17:47 UTC
Added 6
billingRead-onlyRead current free allowances, options with billing off, prices and the account's 7-daytrial. 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 documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).
buy_planWritesBuy 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 days, with no automatic renewal. Without payment, the answer is 402 with the price. Pay with prepaid credit (`X-Credito`) or x402 (`PAYMENT-SIGNATURE` v2 or `X-PAYMENT` v1). Without an account, the verified paying wallet owns the purchase. Use wallet agent authentication to read its plan, or claim it after account sign-in. The `compra` mark prevents repeat credit debits. An x402 nonce can settle only once; keep the receipt after a delivery error.
cancel_planWritesCancel the active plan now. What it added ends, including a paid period that has not started; that period and a purchase under 7 days are refunded. Requires accept_data_removal: true. Send `{ "accept_data_removal": true }`: what the plan added ends now (`account.cancel.losses` in `GET /api/plans` says what), including a period already paid that has not started yet, such as a renewal. A purchase made less than 7 days ago and a paid period that has not started go back the same way they were paid (card or Pix); USDC is refunded by the team.
get_api_x402_checkWritesChecks 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 the price; a paid one gets the reading in the same response, with the payment in `cobranca`. A site that is down is the answer (`ok: false` with `reason`) and is charged: the call was made. When our own probe network fails, the answer is 503 and nothing is charged.
list_plansRead-onlyThe 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`.
pricingRead-onlyCurrent public prices and free allowances; no charge.
Changed 8
contactdescription and input schemaBeforeWrite to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. One route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`). One message every 10 seconds per network: one that arrives sooner waits its turn and then goes out — no error. The message reaches the team by e-mail, with `email` as the reply address. For voice, send multipart/form-data: `dados` is this JSON (up to 32 KiB), and `audio` is one WebM, Ogg or M4A audio file (up to 2 MB). Audio can replace message. The browser records up to two minutes. Audio is attached to the owner's e-mail.
AfterWrite 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 proposal (`tipo`, with the placements of `GET /api/partners`). No captcha, no account, no payment. One message every 10 seconds per network: one that arrives sooner waits its turn and then goes out — no error. The message reaches the team by e-mail, with `email` as the reply address. For voice, send multipart/form-data: `dados` is this JSON (up to 32 KiB), and `audio` is one WebM, Ogg or M4A audio file (up to 2 MB). Audio can replace message. The browser records up to two minutes. Audio is attached to the owner's e-mail.
- Description of
pagamentoBeforenone
After`usdc`, `deposito` or `a_combinar`.
- Description of
create_endpointdescription and input schemaBeforeCreate 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. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `templates` — keep them. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send
`cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is late at 03:01:30, not 24 hours later. `max_duration_sec` catches the other failure: a run that starts and hangs, wh…AfterCreate 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. Read billing before a paid option. A charged request returns HTTP 402. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `templates` — keep them. The second monitor, or an interval below the free minimum, answers **402 with `accepts[]`**: pay and repeat. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec`…
- Description of
interval_secBeforeTolerated silence, in seconds.
AfterTolerated silence, in seconds. Below the free minimum, it costs.
- Description of
create_sitedescriptionBeforeMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `templates` — keep them. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is late at 03:01:30, not 24 hours later. `max_duration_sec` catches the other failure: a run that starts and hangs, which plain silence detection only notices at the next scheduled tim…
AfterMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Read billing before a paid option. A charged request returns HTTP 402. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `templates` — keep them. The second monitor, or an interval below the free minimum, answers **402 with `accepts[]`**: pay and repeat. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is l…
get_endpointdescriptionBeforeStatus 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.
AfterStatus 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 this endpoint carries `duration`: `p50_ms` (the low median, so always a duration that really happened) and `max_ms` over the last runs we measured, computed at read time over the event window we already keep — the list does not pay for it.
ingest_keydescriptionBeforeReturns (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. One key per owner. The key survives signing in: the crontab you deployed keeps working.
AfterReturns (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. One key per owner. Point a whole fleet at `/in/<key>/<slug>` and each job creates its monitor on the first check-in, **inside the free tier** — beyond it the ping answers 402 without creating anything. The key survives signing in: the crontab you deployed keeps working.
list_sitesdescriptionBeforeThe state of every site you monitor (up, down, waiting, paused), with the last check.
AfterThe 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.
ping_ingestdescriptionBeforeSimulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
AfterSimulates 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.
ping_slugdescriptionBeforeCreate a monitor on its first check-in. The same slug uses the same monitor. 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 a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Works by GET or POST.
AfterCreate 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 a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Creation happens **only inside the free tier** (or the trial); past it the ping is a 402 with `accepts[]` and nothing is written — not even the event. Works by GET or POST.
Server instructions
BeforeHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Every tool here is free, within its free limits; when a limit runs out, the tool says so. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
AfterHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.net/api/billing. Read these before choosing a paid operation. Never spend without the user's authority and budget. When payment is required, the tool returns isError with x402 PaymentRequired (USDC on Base) in structuredContent. After authorization, repeat the same call with params._meta["x402/payment"] (@x402/mcp supports this). Prepaid credit uses Authorization: Bearer cred_… or X-Credito. For site payment, open https://hookpulse.net/pricing; use Pix or card only when offered there. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
-
Server instructions changed.
New server instructions
Details, 16 Oct 2026, 07:35 UTC
Server instructions
BeforeHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Every tool here is free, within its free limits; when a limit runs out, the tool says so.
AfterHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Every tool here is free, within its free limits; when a limit runs out, the tool says so. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
-
4 tools added, 19 tools removed and 1 tool changed.
Details, 16 Oct 2026, 01:35 UTC
Added 4
check_siteWritesCheck 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 and the alerts come from the check that runs every minute.
create_siteWritesMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `templates` — keep them. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is late at 03:01:30, not 24 hours later. `max_duration_sec` catches the other failure: a run that starts and hangs, which plain silence detection only notices at the next scheduled tim…
list_sitesRead-onlyThe state of every site you monitor (up, down, waiting, paused), with the last check.
signal_slugRead-onlySend 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. The first signal of a new name creates the monitor, with the same rules and the same `cron`, `tz` and `grace_sec` as the plain ping by name.
Removed 19
create_collectionAdds compatible measurements to a previously detected device. First create /api/ambientes and submit its environment report. Reference that ambiente_id here; its saved name and group are authoritative. Same device+measurement returns the existing stream instead of duplicating it. A profile adds only compatible measurements. Up to 200 collections per owner. The signed collection id writes only its own measurement stream.
create_device_inputCreate or rotate an authenticated collector channel for this device. Ownership is checked before the app asks the input central. The server chooses the channel id and authenticates batches only against a hash of the collector credential. The whole setup this call returns — credential included — is also saved, encrypted with a key only the input central holds and bound to that credential, so the owner can read it again with GET /api/ambientes/:id/inputs/:collector/setup. The credential does not expire: a device that stays off for weeks reconnects with it. It stops working only when a new configuration rotates it or the channel is removed. A repeated call for the same collector rotates the credential, replaces the saved setup and replaces `monitoring` with the list sent — that is how the monitored scope is edited — so the configuration on the device stops authenticating until it is replaced; a paused channel stays paused. DNS selects the receiver; it never authenticates the device.
create_environmentRegister a device UUID before discovery and collector selection. Registers one device (maximum 25 per owner), creating a guest if needed. The UUID is the one-hour discovery capability; it is not a telemetry credential. Choose passos.posix or passos.powershell for the TARGET terminal. The checks only display allowlisted system facts and install nothing.
delete_collectionRemoves one measurement and frees that slot on the device. What disappears is the OWNERSHIP: your list, the authority to read that series, and the unique slot that measurement holds on that environment — so you can add it again later. Readings already stored at the ingest origin stay there until their own retention. The machine keeps sending: the symbol is signed and stands on its own there, which is why the answer carries `remover`, the command that takes the line out of the crontab. Use `ativa:false` instead when you only want to stop looking.
delete_device_inputRevokes and removes one collector channel from a device. The input central removes only a channel of the same owner. This stops new authenticated input and removes the channel from the device list — also for a channel whose device was already deleted. It does not uninstall or stop the collector on the device (`uninstall.remove` in GET /api/ambientes/:id/inputs is the command for that), and stored measurements remain subject to their retention policy.
delete_environmentRemoves a device and every measurement on it, in one call. One call, not one per measurement — the same reason `GET /api/coletas/serie` exists. What goes away is the ownership: your list, the authority to read those series, and the slots those measurements held, so the device can be registered again. Readings already stored at the ingest origin stay there until their own retention, and the machine keeps sending: the symbols are signed and stand on their own there. That is why the answer carries `remover`, one command per measurement that had a cron line. The device's collector channels are revoked first; if the input central cannot confirm that, nothing is deleted (503) and the call can be repeated, so no channel is left receiving data without a device.
get_collection_seriesThe latest readings of one device, for the screen that draws it. Authorised by YOUR session, never by the symbol in the crontab. A device that is not yours answers 404 exactly like one that does not exist — telling the two apart would confirm to a stranger that the id exists — 401 is only for sending no credential at all, which tells the caller what they already know. When the ingest origin cannot be read the answer is 503, not an empty series: a screen must say "I could not read now", never let you believe your machine stopped. Readings are reused for up to 60 seconds. Poll no faster than once per minute in steady use; `poll_after_sec` is the minimum wait for this response. During the first minute after registration an empty series may be checked every 5 seconds. Do not overlap requests. On 429 or 503, respect `Retry-After` and `retry_after_sec`, increase the delay after repeated failures, and keep the last successful reading. Changing n does not bypass reuse or capacity limits.
get_device_input_batchOne received batch, decoded: its series with labels and values, or its NCPA checks. Remote Write (1.0 and 2.0), OTLP (protobuf or JSON) and NRDP become the same shape: `series` (`name`, `labels`, `points` as `[milliseconds, value]`, and `type`/`unit`/`help` when the collector sent them; OTLP points also carry `resource`, an index into `resources`) or `checks` for NCPA (`host`, `service`, `state` 0–3, `output`, `perfdata`). A value JSON cannot hold comes as a string: `"NaN"`, `"+Inf"`, `"-Inf"` or `"stale"`. Very large batches keep the first 5,000 series (`truncated`). `newer`/`older` are the neighbouring batch ids, for moving through the history.
get_device_input_setupThe saved setup of one collector channel: the configuration in use, its files and steps. Returns the setup generated last for this channel — the one whose credential is accepted now — exactly as POST /api/ambientes/:id/inputs returned it, so the files can be copied or installed again without rotating the credential. It carries the credential: only the device owner gets it, one channel per request, never cached; list routes never include it. 404 `setup_not_saved` when the channel was generated before setups were saved, or was removed; 409 `setup_unreadable` when the input central can no longer open it. In both cases generate a new setup with POST /api/ambientes/:id/inputs.
get_environmentRead the detected environment and compatible measurements.
list_collectionsLists your measurements with commands adapted to each saved device environment. Two views of the same thing: `coletas` is one entry per measurement, `equipamentos` is one per machine with a SINGLE command that does all of its measurements and a SINGLE cron line. Use the device one unless you really want a single measurement on its own. Commands are generated only from a detected environment. Legacy collections without one keep their readings, but comandos.agora/agenda are null until a compatible environment is provided. Curl, wget and Python 3 follow the detected capabilities; Windows disk uses PowerShell. comandos.agora is a readable multiline block; run the whole block together. A separate cron line is offered only when crontab exists. Unsupported formats are never guessed.
list_device_input_historyThe batches this collector sent, newest first — filtered and paginated on the server. Every batch the input central received for this channel, as it arrived: when, the protocol, the result (`stored`; `rejected` by the receiver, with the reason; or `discarded` while the channel was paused, when its data is not kept), the answer given to the collector, the size, and how many series and samples it carried. The central keeps the newest batches of each channel up to the limits in `limits` (count, bytes and days); older ones leave as new ones arrive, and removing the channel deletes them. `q` searches metric names — host and service names for NCPA — by opening the batches newest first within a time budget: `search.complete` says whether all candidates were read, and repeating the call continues faster. Open one batch with GET /api/ambientes/:id/inputs/:collector/history/:batch.
list_device_inputsList this device's collector channels, their state and their live numbers.
list_environmentsSaved environments owned by the current account or guest; empty without a session.
list_input_fleetEvery collector channel of the caller, with state and live numbers, in one response. One call for the whole fleet — one query to the time-series store for all channels, never one per device. It is the same function the dashboard subscribes to over the socket (`/api/inputs/serie`), where the input central then pushes `inputs.updated` and `inputs.removed` events; integrators get the same data here without the socket. A failed input-central request or an invalid fleet response returns 503 inputs_unavailable, never a successful empty fleet. Fleet reads give the input-central exchange, including its response body, a 750 ms deadline. The optional time-series query has a 400 ms deadline; when it is unavailable or too slow, channels are preserved with stats null. An authenticated owner with no channels still gets an empty list.
report_environmentPreview or save the allowlisted discovery report for one device. Send terminal and saidas (step id to pasted output), initially with conferir:true. Preview returns normalized dados, additional passos and pronto without writing. Omit conferir to save when complete. Only allowlisted facts are saved, never raw commands. First report wins within one hour; identical retries do not rewrite. The discovery never creates a legacy measurement, sends a reading, installs software or creates a schedule. With Accept: text/plain the receipt is only `ok`.
set_device_input_activePauses or resumes one collector channel. Pausing keeps the channel, its credential and its configuration: batches the collector sends while paused are accepted and discarded, so nothing is stored or measured and the collector does not retry in a loop. Resuming stores the next batch again. The input central changes only a channel of the same owner, including one whose device was already deleted.
update_collectionRenames one measurement, or stops and resumes reading it. The id never changes: it is the write symbol already sitting in a crontab, and renaming on a screen must not send anyone back to the machine to edit a line. Send only what you are changing; anything omitted stays as it is. `ativa:false` takes the measurement out of the fleet read — it keeps its history and its commands, stops costing a query, and comes back with `ativa:true`. It does NOT silence the machine: the symbol is signed and stands on its own at the ingest origin, so a device keeps sending until you remove its cron line. The answer is the collection as it now stands — draw the screen from it, not from a local copy.
update_environmentRenames a device, and its measurements along with it. One machine has one name. The measurements carry a copy of it, so renaming here renames them too — leaving the old name on them would show the same machine twice in a list that groups by device. Its collector channels take the new name and group too in `GET /api/coletas` (`inputs[]`), and the group decides which dashboard tab the device is under. Send only what changes; what you omit stays. The detected environment is never rewritten: it is evidence of what that machine reported.
Changed 1
create_endpointdescriptionBeforeCreate 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. This response is the only one that shows the monitor's `token` and the `templates` — keep them. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is late at 03:01:30, not 24 hours later. `max_duration_sec` catches the other failure: a run that starts and hangs, which plain silence detection only notices at the next scheduled time.
AfterCreate 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. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `templates` — keep them. A miss alerts at most once per 24h — or per `alert_repeat_sec`, or per interval, whichever is longer. Send `cron`+`tz`+`grace_sec` instead of `interval_sec` for a real schedule: a 03:00 backup is late at 03:01:30, not 24 hours later. `max_duration_sec` catches the other failure: a run that starts and hangs, wh…
-
1 tool changed.
Details, 15 Oct 2026, 16:40 UTC
Changed 1
contactThe 10 newest entries show every detail; older ones show names only.
-
5 tools removed and 39 tools changed. Server instructions changed.
New server instructions
Details, 15 Oct 2026, 04:32 UTC
Removed 5
billingbuy_plancancel_planlist_planspricingChanged 39
api_indexcontactcreate_collectioncreate_device_inputcreate_endpointcreate_environmentcreate_guestdelete_collectiondelete_device_inputdelete_endpointdelete_environmentget_collection_seriesget_device_input_batchget_device_input_setupget_endpointget_environmenthealthimport_crontabingest_keyingest_key_rotatelist_collectionslist_device_input_historylist_device_inputslist_endpointslist_environmentslist_eventslist_input_fleetlist_templatesping_ingestping_slugand 9 moreThe 10 newest entries show every detail; older ones show names only.
-
1 tool changed.
Details, 14 Oct 2026, 22:32 UTC
Changed 1
contactThe 10 newest entries show every detail; older ones show names only.
-
2 tools changed.
Details, 14 Oct 2026, 16:35 UTC
Changed 2
buy_planlist_plansThe 10 newest entries show every detail; older ones show names only.
-
Tracking started: 44 tools.
FAQ
Can I paste mcp.tc/i/hookpulse into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://hookpulse.net/mcp, so your client talks to HookPulse directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does HookPulse need an API key or a sign-in?
No. HookPulse doesn’t ask for an account or key.
Is HookPulse a remote or a local server?
Remote. HookPulse (WRP Consultoria e Informática) hosts it at https://hookpulse.net/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can HookPulse do?
It has 29 tools, including list_plans, buy_plan and cancel_plan. You can create monitors with a cron schedule or fixed check-in interval, import a crontab and propose one monitor per line and signal start, failure or shell exit code for a run.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to HookPulse?
Yes. HookPulse’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read HookPulse’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with HookPulse (WRP Consultoria e Informática). This page was built from HookPulse’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.