HookPulse
Server MCP di HookPulse (WRP Consultoria e Informática)
Monitora cron job, backup e automazioni con check-in dead-man, avvisi di mancata esecuzione e un feed di stato.
Collegati a HookPulse
Non serve un account. Collegati con l’URL di HookPulse:
Incollalo in qualsiasi client che supporti i server MCP remoti. Il tuo client parla direttamente con HookPulse (WRP Consultoria e Informática), non attraverso mcp.tc.
Condividi questo server
Apre questa pagina, con l’URL e i passaggi di configurazione.
mcp.tc/i/hookpulseDescrizione
HookPulse è un dead-man switch per le routine pianificate. Crei monitor con un intervallo o una pianificazione cron, le routine inviano un ping a un URL di ingest e scatta un avviso quando i check-in si interrompono. Gli strumenti permettono anche di segnalare avvio, errore e codici di uscita, importare un crontab, gestire input e misurazioni dei collector dei dispositivi, usare un feed di stato, consultare piani e fatturazione.
Funziona come endpoint Streamable HTTP ospitato su hookpulse.net/mcp. L’endpoint risponde a richieste anonime senza accesso né chiave API; i monitor sono legati a un token guest o a una sessione di account. Il superamento della quota restituisce una risposta 402 con i dettagli di pagamento x402 (USDC) e i piani a pagamento durano 30 giorni.
Cosa puoi fare
- Creare monitor con una pianificazione cron o un intervallo fisso di check-in
- Importare un crontab e proporre un monitor per ogni riga
- Segnalare avvio, errore o codice di uscita della shell di un’esecuzione
- Elencare i monitor e leggere gli eventi ping recenti
- Gestire gli ambienti dei dispositivi e gli input dei collector
- Ottenere un feed di stato pubblico JSON/RSS di tutti i monitor
- Vedere i prezzi e acquistare o annullare un piano
Tool 29
list_plansSola letturaList plans
buy_planScriveBuy plan
cancel_planScriveCancel plan
api_indexSola letturaIndice dell’API
healthSola letturaStato di salute
create_guestScriveCrea un token guest usato per raggiungere i tuoi monitor.
list_endpointsSola letturaElenca gli endpoint di monitor del guest o della sessione.
create_endpointScriveCrea un monitor con una pianificazione cron o a intervallo.
create_siteScriveCrea un sito
check_siteScriveControlla il sito
list_sitesSola letturaElenca i siti
import_crontabScriveLegge un crontab e propone un monitor per ogni riga pianificata.
Mostra altri 17 tool
get_endpointSola letturaOttiene lo stato di un endpoint, compresa la prossima esecuzione attesa.
delete_endpointPuò eliminareRimuove l’endpoint di un proprietario.
list_eventsSola letturaElenca gli ultimi ping di ingest.
ping_ingestSola letturaSimula un check-in cron sull’URL di ingest.
signal_startSola letturaRegistra l’avvio di un’esecuzione senza azzerare il timer dead-man.
signal_failSola letturaRegistra un’esecuzione fallita così il prossimo controllo invia un avviso.
signal_exit_codeSola letturaInvia uno stato di uscita della shell; 0 è un ping, da 1 a 255 un errore.
ingest_keySola letturaOttiene o genera la chiave per creare automaticamente monitor al primo ping.
ingest_key_rotatePuò eliminareRuota la chiave di ingest in modo che la vecchia non possa creare monitor.
ping_slugSola letturaCrea un monitor al primo check-in usando uno slug.
signal_slugSola letturaSegnala lo slug
pricingSola letturaPricing
status_feed_urlSola letturaOttiene l’URL del feed di stato pubblico JSON/RSS per tutti gli endpoint.
status_feed_rotatePuò eliminareRuota il token del feed di stato.
list_templatesSola letturaMostra gli snippet di ingest e i body JSON inviati in caso di mancata esecuzione.
contactScriveContatto
get_api_x402_checkScriveGet API X402 check
Letti dal server attivo (18 nov 2026). Sola lettura, Scrive e Può eliminare sono indicazioni dichiarate dal server; è il tuo client a decidere se chiederti conferma prima di eseguire un tool.
Prompt di esempio
Crea un monitor HookPulse per il mio backup notturno, atteso ogni 24 ore.
Importa questo crontab e proponi un monitor per ogni job.
Mostra gli ultimi eventi ping del mio monitor del backup.
Dammi l’URL del feed di stato di tutti i miei monitor.
Configurazione
Ogni client si collega a hookpulse.net. Scegli il tuo; la pagina ricorda la tua scelta.
Claude Code
- Eseguilo in un terminale, nella cartella del tuo progetto:
claude mcp add --transport http hookpulse https://hookpulse.net/mcp- Avvia Claude Code e digita
/mcp. hookpulse dovrebbe risultare collegato.
Aggiungi --scope user per renderlo disponibile in tutti i progetti, non solo in questo.
Claude Desktop
- Apri Customize → Connectors, fai clic su + Add, poi su Add custom connector.
- Chiamalo HookPulse e incolla questo URL:
https://hookpulse.net/mcp- Fai clic su Add. I suoi tool compaiono nel menu degli strumenti della chat.
Il file di configurazione JSON di Claude Desktop avvia solo server locali. I server remoti passano dai Connectors, e i connettori che aggiungi su claude.ai compaiono anche qui.
claude.ai
- Apri il modulo dei connettori su claude.ai. Questo pulsante compila nome e URL per te:
Aggiungi a claude.ai (si apre in una nuova scheda)
- Controlla che l’URL sia
https://hookpulse.net/mcpe fai clic su Add. - Attivalo in una chat dal menu degli strumenti.
I piani gratuiti consentono un connettore personalizzato. Nei piani Team ed Enterprise lo aggiunge un owner in Organization settings → Connectors.
ChatGPT
- Su chatgpt.com vai su Plugins, seleziona + e poi Add custom MCP server.
- Inserisci un nome per il server.
- In Connection incolla
https://hookpulse.net/mcpcome URL del server, poi come autenticazione scegli No authentication. - Spunta I understand and want to continue e poi seleziona Create as a plugin.
Se puoi aggiungere un server MCP personalizzato dipende dal tuo piano ChatGPT e dai permessi del tuo workspace (nei workspace Business possono farlo admin e owner).
Cursor
Aggiungi a Cursor (si apre in una nuova scheda)
Oppure aggiungilo a mano in ~/.cursor/mcp.json (tutti i progetti) o in .cursor/mcp.json (questo progetto):
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}VS Code
Installa in VS Code (si apre in una nuova scheda)
Oppure da un terminale:
code --add-mcp '{"name":"hookpulse","type":"http","url":"https://hookpulse.net/mcp"}'Oppure fai commit nel repository in .vscode/mcp.json:
{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Devin Desktop
- Aggiungilo a
~/.config/devin/mcp_config.json(macOS e Linux) o a%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"hookpulse": {
"serverUrl": "https://hookpulse.net/mcp"
}
}
}- Aggiorna l’elenco dei server MCP in Cascade.
Devin Desktop è il nuovo nome di Windsurf. Per i server remoti legge serverUrl (o url).
Codex
codex mcp add hookpulse --url https://hookpulse.net/mcpOppure modifica direttamente ~/.codex/config.toml:
[mcp_servers.hookpulse]
url = "https://hookpulse.net/mcp"Gemini CLI
gemini mcp add --transport http hookpulse https://hookpulse.net/mcpCosì lo aggiungi al progetto corrente. Aggiungi -s user per usarlo ovunque.
Qualsiasi client
La maggior parte dei client accetta questa forma. Alcuni chiamano diversamente il campo dell’URL: serverUrl in Devin Desktop, httpUrl nel file di impostazioni di Gemini CLI.
{
"mcpServers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Zed mette i server sotto context_servers nelle sue impostazioni. Cline ha bisogno di "type": "streamableHttp", altrimenti presume SSE.
Il tuo client avvia solo server locali? Collegalo con npx -y mcp-remote https://hookpulse.net/mcp.
Embed
Mostra HookPulse in un README o sul tuo sito. Ogni embed rimanda a questa pagina, usa l’URL del server stesso e non imposta cookie. Come funzionano gli embed
Card, iframe e JSON sono in inglese. Aggiungi ?lang=it, fr, de o es al loro indirizzo per un’altra lingua.
Badge per il README
[](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>Segue la modalità chiara o scura di chi legge. Aggiungi ?theme=light o ?theme=dark per fissarla, oppure ?style=compact per mostrare il simbolo senza la scritta.
Card per il sito
<script src="https://mcp.tc/w/hookpulse.js" async></script>La card compare dove si trova il tag. Aggiungi data-theme="dark" o data-size="compact" al tag per cambiarla. Il file contiene tutto ciò che serve, quindi non fa altre richieste e non imposta cookie.
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>Usalo nelle pagine che non consentono script. Aggiungi ?theme=light o ?theme=dark all’indirizzo per fissare i colori.
JSON
La scheda come dati per le tue pagine e i tuoi strumenti: nome, descrizione breve, URL del server, tool e i link «Add to». Qualsiasi sito può leggerla (CORS aperto).
https://mcp.tc/i/hookpulse.jsonPrompt per l’AI
Incollalo in un assistente di programmazione con l’AI, come Claude Code o Cursor, e aggiungerà la card di HookPulse al tuo sito.
Aggiungi al mio sito la card di mcp.tc per HookPulse, un server MCP. È un solo script statico: niente build, nessun pacchetto da installare, nessun cookie.
Metti questo tag dove deve comparire la card. La card appare subito prima del tag:
```html
<script src="https://mcp.tc/w/hookpulse.js" async></script>
```
Per mostrarla altrove, metti lì questo segnaposto e carica lo stesso script una volta sola, per esempio prima di `</body>`. Lascia il link al suo interno: lo vede chi non ha JavaScript.
```html
<div data-mcptc="hookpulse"><a href="https://mcp.tc/i/hookpulse">HookPulse on mcp.tc</a></div>
```
Opzioni:
- `data-theme="light"` o `"dark"` sul tag o sul segnaposto fissa i colori. Senza l’attributo, la card segue la modalità chiara o scura di chi visita.
- `data-size="compact"` dà una card più piccola, senza la descrizione breve.
- La variabile CSS `--mcptc-max-width` sul segnaposto o su un elemento padre imposta la larghezza (predefinita `520px`).
- `?lang=` nell’URL dello script imposta la lingua della card: `en`, `it`, `fr`, `de` o `es`.
Se il sito ha una Content Security Policy, consenti `script-src https://mcp.tc` e `img-src data:` (l’icona è inline).
Per un README o altra documentazione in Markdown, usa invece il badge:
```markdown
[](https://mcp.tc/i/hookpulse)
```
Riferimento: https://mcp.tc/it/embedCronologia delle modifiche
Leggiamo l’elenco dei tool di questo server ogni 3 ore e registriamo cosa cambia. Ultima lettura: 18 nov 2026, 05:39 UTC.
-
1 tool rimosso e 1 tool modificato.
Dettagli, 10 nov 2026, 17:54 UTC
Rimossi 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`).
Modificati 1
pricingdescrizione e schema di inputPrimaCurrent publicprices andfree allowances; no charge.DopoRead 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 tool modificati.
Dettagli, 5 nov 2026, 05:53 UTC
Modificati 14
check_siteschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
create_siteschema di inputdelete_endpointschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
get_endpointschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
healthdescrizionePrimaLiveness.DopoRead service liveness before using HookPulse. Returns the health response; does not check a monitor.
import_crontabdescrizione e schema di inputPrimaReads 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.
DopoReads 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"…
- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
ingest_keyschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
ingest_key_rotateschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
list_endpointsschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
list_eventsschema di input- Descrizione di
guest_tokenPrimanessuno
DopoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descrizione di
list_sitesping_slugstatus_feed_rotatestatus_feed_url -
Istruzioni del server modificate.
Nuove istruzioni del server
Dettagli, 4 nov 2026, 02:48 UTC
Istruzioni del server
PrimaHookPulse 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.DopoUse 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 tool modificati.
Dettagli, 2 nov 2026, 11:52 UTC
Modificati 2
ping_slugschema di inputsignal_slugschema di input
-
2 tool modificati.
Dettagli, 2 nov 2026, 05:48 UTC
Modificati 2
create_endpointdescrizione e schema di inputPrimaCreate 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.
DopoCreate 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.
- Non più obbligatori:
guest_token - Descrizione di
guest_tokenPrimanessuno
DopoExisting owner token, if available.
- Descrizione di
alert_toPrimaE-mail to alert on a miss; withoutit, the account isalerted.DopoAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- Non più obbligatori:
create_sitedescrizione e schema di inputPrimaMonitor 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.
DopoMonitor 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.
- Non più obbligatori:
guest_token - Descrizione di
guest_tokenPrimanessuno
DopoExisting owner token, if available.
- Descrizione di
alert_toPrimaE-mail to alert on a miss; withoutit, the account isalerted.DopoAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- Non più obbligatori:
-
3 tool modificati. Istruzioni del server modificate.
Nuove istruzioni del server
Dettagli, 1 nov 2026, 17:49 UTC
Modificati 3
billingdescrizionePrimaRead 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`).DopoRead 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_endpointdescrizionePrimaCreate 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`…DopoCreate 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_sitedescrizionePrimaMonitor 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…DopoMonitor 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.
Istruzioni del server
PrimaHookPulse 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.
DopoHookPulse 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 modificato.
Dettagli, 31 ott 2026, 14:50 UTC
Modificati 1
cancel_plandescrizionePrimaCancel 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.DopoCancel 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 tool aggiunti e 8 tool modificati. Istruzioni del server modificate.
Nuove istruzioni del server
Dettagli, 30 ott 2026, 17:47 UTC
Aggiunti 6
billingSola letturaRead 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_planScriveBuy 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_planScriveCancel 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_checkScriveChecks 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_plansSola letturaThe 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`.
pricingSola letturaCurrent public prices and free allowances; no charge.
Modificati 8
contactdescrizione e schema di inputPrimaWrite 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.
DopoWrite 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.
- Descrizione di
pagamentoPrimanessuno
Dopo`usdc`, `deposito` or `a_combinar`.
- Descrizione di
create_endpointdescrizione e schema di inputPrimaCreate 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…DopoCreate 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`…
- Descrizione di
interval_secPrimaTolerated silence, in seconds.
DopoTolerated silence, in seconds. Below the free minimum, it costs.
- Descrizione di
create_sitedescrizionePrimaMonitor 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…
DopoMonitor 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_endpointdescrizionePrimaStatus 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.
DopoStatus 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_keydescrizionePrimaReturns (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.
DopoReturns (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_sitesdescrizionePrimaThe state of every site you monitor (up, down, waiting, paused), with the last check.
DopoThe 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_ingestdescrizionePrimaSimulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
DopoSimulates 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_slugdescrizionePrimaCreate 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.
DopoCreate 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.
Istruzioni del server
PrimaHookPulse 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.
DopoHookPulse 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.
-
Istruzioni del server modificate.
Nuove istruzioni del server
Dettagli, 16 ott 2026, 07:35 UTC
Istruzioni del server
PrimaHookPulse 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.
DopoHookPulse 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 tool aggiunti, 19 tool rimossi e 1 tool modificato.
Dettagli, 16 ott 2026, 01:35 UTC
Aggiunti 4
check_siteScriveCheck 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_siteScriveMonitor 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_sitesSola letturaThe state of every site you monitor (up, down, waiting, paused), with the last check.
signal_slugSola letturaSend 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.
Rimossi 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.
Modificati 1
create_endpointdescrizionePrimaCreate 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.
DopoCreate 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 modificato.
Dettagli, 15 ott 2026, 16:40 UTC
Modificati 1
contactLe 10 voci più recenti mostrano ogni dettaglio; le più vecchie mostrano solo i nomi.
-
5 tool rimossi e 39 tool modificati. Istruzioni del server modificate.
Nuove istruzioni del server
Dettagli, 15 ott 2026, 04:32 UTC
Rimossi 5
billingbuy_plancancel_planlist_planspricingModificati 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_sluge altri 9Le 10 voci più recenti mostrano ogni dettaglio; le più vecchie mostrano solo i nomi.
-
1 tool modificato.
Dettagli, 14 ott 2026, 22:32 UTC
Modificati 1
contactLe 10 voci più recenti mostrano ogni dettaglio; le più vecchie mostrano solo i nomi.
-
2 tool modificati.
Dettagli, 14 ott 2026, 16:35 UTC
Modificati 2
buy_planlist_plansLe 10 voci più recenti mostrano ogni dettaglio; le più vecchie mostrano solo i nomi.
-
Inizio del tracciamento: 44 tool.
Domande frequenti
Posso incollare mcp.tc/i/hookpulse nel mio client MCP?
No. I link di mcp.tc sono pagine, non indirizzi di server. Collegati con https://hookpulse.net/mcp, così il tuo client parla direttamente con HookPulse. Il link rapido serve per condividere: apre questa pagina, con i passaggi di configurazione per ogni client.
HookPulse richiede una chiave API o un accesso?
No. HookPulse non chiede account né chiavi.
HookPulse è un server remoto o locale?
Remoto. Lo ospita HookPulse (WRP Consultoria e Informática) a https://hookpulse.net/mcp, e usa Streamable HTTP. Non c’è nulla da installare.
Cosa può fare HookPulse?
Ha 29 tool, tra cui list_plans, buy_plan e cancel_plan. Puoi creare monitor con una pianificazione cron o un intervallo fisso di check-in, importare un crontab e proporre un monitor per ogni riga e segnalare avvio, errore o codice di uscita della shell di un’esecuzione.
Quali client possono usarlo?
Qualsiasi client che supporta i server MCP remoti: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed e altri. I passaggi di configurazione li coprono tutti.
mcp.tc tiene traccia delle modifiche di HookPulse?
Sì. La sezione Cronologia di HookPulse mostra ogni modifica che troviamo ai suoi tool, fino a descrizioni e parametri, più le nuove versioni e le modifiche di chi lo gestisce. Segui la scheda per ricevere un’email quando cambia.
Chi ha scritto questa pagina?
Il robot di mcp.tc ha letto i metadati di HookPulse (il suo handshake MCP, l’elenco dei tool e le pagine pubbliche), e un modello di AI ne ha ricavato il testo. Una persona esamina tutto ciò che i controlli non riescono a confermare. Il testo può comunque contenere errori, quindi se ne trovi uno usa Segnala questa scheda su questa pagina. Questa traduzione è stata fatta da un modello di AI a partire dal testo inglese.
mcp.tc non è affiliato a HookPulse (WRP Consultoria e Informática). Questa pagina è stata creata a partire dai metadati pubblici di HookPulse (ultimo controllo: 18 nov 2026), e la descrizione l’ha scritta un modello di AI, quindi può contenere errori. Nomi e marchi appartengono ai rispettivi titolari. Qualcosa non va? Segnala questa scheda. La traduzione è stata fatta da un modello di AI a partire dal testo inglese.