HookPulse
Serveur MCP par HookPulse (WRP Consultoria e Informática)
Surveiller les tâches cron, sauvegardes et automatisations avec des check-ins dead-man, des alertes d’absence et un flux d’état.
Connecter HookPulse
Aucun compte nécessaire. Connectez votre client à l’URL de HookPulse :
Collez-la dans n’importe quel client compatible avec les serveurs MCP distants. Votre client parle directement à HookPulse (WRP Consultoria e Informática), sans passer par mcp.tc.
Partager ce serveur
Ouvre cette page, avec l’URL et les étapes de configuration.
mcp.tc/i/hookpulsePrésentation
HookPulse est un dead-man switch pour les routines planifiées. Vous créez des moniteurs avec un intervalle ou une planification cron, les routines envoient un ping à une URL d’ingestion, et une alerte se déclenche lorsque les check-ins s’arrêtent. Les outils permettent aussi de signaler le démarrage, l’échec et les codes de sortie, d’importer une crontab, de gérer les entrées et mesures des collecteurs d’appareils, ainsi que de consulter un flux d’état, les offres et la facturation.
Il s’exécute comme un endpoint Streamable HTTP hébergé à hookpulse.net/mcp. L’endpoint répond aux requêtes anonymes sans compte ni clé API ; les moniteurs sont liés à un jeton invité ou à une session de compte. Un dépassement de quota renvoie une réponse 402 avec les détails de paiement x402 (USDC), et les offres payantes durent 30 jours.
Ce que vous pouvez faire
- Créer des moniteurs avec une planification cron ou un intervalle de check-in fixe
- Importer une crontab et proposer un moniteur par ligne
- Signaler le démarrage, l’échec ou le code de sortie shell d’une exécution
- Lister les moniteurs et lire les derniers événements de ping
- Gérer les environnements d’appareils et les entrées des collecteurs
- Obtenir un flux d’état public JSON/RSS de tous les moniteurs
- Consulter les tarifs et acheter ou annuler une offre
Outils 29
list_plansLecture seuleList plans
buy_planÉcritureBuy plan
cancel_planÉcritureCancel plan
api_indexLecture seuleIndex de l’API
healthLecture seuleÉtat de santé
create_guestÉcritureCréer un jeton invité pour accéder à vos moniteurs.
list_endpointsLecture seuleLister les endpoints de moniteurs de l’invité ou de la session.
create_endpointÉcritureCréer un moniteur avec une planification cron ou par intervalle.
create_siteÉcritureCréer un site
check_siteÉcritureVérifier le site
list_sitesLecture seuleLister les sites
import_crontabÉcritureLire une crontab et proposer un moniteur par ligne planifiée.
Afficher 17 outils de plus
get_endpointLecture seuleObtenir l’état d’un endpoint, y compris la prochaine exécution attendue.
delete_endpointPeut supprimerSupprimer l’endpoint d’un propriétaire.
list_eventsLecture seuleLister les derniers pings d’ingestion.
ping_ingestLecture seuleSimuler un check-in cron sur l’URL d’ingestion.
signal_startLecture seuleEnregistrer le démarrage d’une exécution sans réinitialiser le minuteur dead-man.
signal_failLecture seuleEnregistrer une exécution échouée pour que la prochaine vérification envoie une alerte.
signal_exit_codeLecture seuleEnvoyer un code de sortie shell ; 0 est un ping, 1 à 255 un échec.
ingest_keyLecture seuleObtenir ou générer la clé de création automatique de moniteurs au premier ping.
ingest_key_rotatePeut supprimerRenouveler la clé d’ingestion pour que l’ancienne ne puisse plus créer de moniteurs.
ping_slugLecture seuleCréer un moniteur au premier check-in à l’aide d’un slug.
signal_slugLecture seuleSignaler le slug
pricingLecture seulePricing
status_feed_urlLecture seuleObtenir l’URL du flux d’état public JSON/RSS de tous les endpoints.
status_feed_rotatePeut supprimerRenouveler le jeton du flux d’état.
list_templatesLecture seuleAfficher les extraits d’ingestion et les corps JSON envoyés en cas d’absence.
contactÉcritureContact
get_api_x402_checkÉcritureGet API X402 check
Lus directement sur le serveur le 18 nov. 2026. Lecture seule, Écriture et Peut supprimer sont des indications déclarées par le serveur ; c’est votre client qui décide de vous demander confirmation avant d’exécuter un outil.
Exemples de prompts
Crée un moniteur HookPulse pour ma sauvegarde de nuit, attendue toutes les 24 heures.
Importe cette crontab et propose un moniteur pour chaque tâche.
Montre-moi les derniers événements de ping de mon moniteur de sauvegarde.
Donne-moi l’URL du flux d’état de tous mes moniteurs.
Configuration
Chaque client se connecte à hookpulse.net. Choisissez le vôtre ; la page retient votre choix.
Claude Code
- Lancez ceci dans un terminal, dans le dossier de votre projet :
claude mcp add --transport http hookpulse https://hookpulse.net/mcp- Démarrez Claude Code et tapez
/mcp. hookpulse devrait apparaître comme connecté.
Ajoutez --scope user pour le rendre disponible dans tous vos projets, pas seulement celui-ci.
Claude Desktop
- Ouvrez Customize → Connectors, cliquez sur + Add, puis sur Add custom connector.
- Nommez-le HookPulse et collez cette URL :
https://hookpulse.net/mcp- Cliquez sur Add. Ses outils apparaissent dans le menu des outils de la conversation.
Le fichier de configuration JSON de Claude Desktop ne lance que des serveurs locaux. Les serveurs distants passent par les Connectors, et les connecteurs ajoutés sur claude.ai apparaissent aussi ici.
claude.ai
- Ouvrez le formulaire des connecteurs sur claude.ai. Ce bouton remplit le nom et l’URL pour vous :
Ajouter à claude.ai (s’ouvre dans un nouvel onglet)
- Vérifiez que l’URL est
https://hookpulse.net/mcpet cliquez sur Add. - Activez-le dans une conversation depuis le menu des outils.
Les offres gratuites permettent un connecteur personnalisé. Sur les offres Team et Enterprise, un propriétaire l’ajoute dans Organization settings → Connectors.
ChatGPT
- Sur chatgpt.com, allez dans Plugins, sélectionnez +, puis Add custom MCP server.
- Saisissez un nom pour le serveur.
- Dans Connection, collez
https://hookpulse.net/mcpcomme URL du serveur, puis pour l’authentification choisissez No authentication. - Cochez I understand and want to continue, puis sélectionnez Create as a plugin.
La possibilité d’ajouter un serveur MCP personnalisé dépend de votre forfait ChatGPT et des autorisations de votre espace de travail (dans les espaces Business, les administrateurs et les propriétaires le peuvent).
Cursor
Ajouter à Cursor (s’ouvre dans un nouvel onglet)
Ou ajoutez-le à la main dans ~/.cursor/mcp.json (tous les projets) ou .cursor/mcp.json (ce projet) :
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}VS Code
Installer dans VS Code (s’ouvre dans un nouvel onglet)
Ou depuis un terminal :
code --add-mcp '{"name":"hookpulse","type":"http","url":"https://hookpulse.net/mcp"}'Ou committez-le dans le dépôt, dans .vscode/mcp.json :
{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Devin Desktop
- Ajoutez-le à
~/.config/devin/mcp_config.json(macOS et Linux) ou%APPDATA%\devin\mcp_config.json(Windows) :
{
"mcpServers": {
"hookpulse": {
"serverUrl": "https://hookpulse.net/mcp"
}
}
}- Actualisez la liste des serveurs MCP dans Cascade.
Devin Desktop est le nouveau nom de Windsurf. Pour les serveurs distants, il lit serverUrl (ou url).
Codex
codex mcp add hookpulse --url https://hookpulse.net/mcpOu modifiez directement ~/.codex/config.toml :
[mcp_servers.hookpulse]
url = "https://hookpulse.net/mcp"Gemini CLI
gemini mcp add --transport http hookpulse https://hookpulse.net/mcpCela l’ajoute au projet en cours. Ajoutez -s user pour l’utiliser partout.
Tout client
La plupart des clients acceptent cette forme. Certains nomment autrement le champ de l’URL : serverUrl dans Devin Desktop, httpUrl dans le fichier de réglages de Gemini CLI.
{
"mcpServers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Zed place les serveurs sous context_servers dans ses réglages. Cline a besoin de "type": "streamableHttp", sinon il suppose SSE.
Votre client ne lance que des serveurs locaux ? Reliez-le avec npx -y mcp-remote https://hookpulse.net/mcp.
Intégrer
Affichez HookPulse dans un README ou sur votre site. Chaque intégration renvoie à cette page, utilise l’URL du serveur et ne dépose aucun cookie. Comment fonctionnent les intégrations
La carte, l’iframe et le JSON sont en anglais. Ajoutez ?lang=it, fr, de ou es à leur adresse pour une autre langue.
Badge pour 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>Il suit le mode clair ou sombre du lecteur. Ajoutez ?theme=light ou ?theme=dark pour le fixer, ou ?style=compact pour afficher le symbole sans le nom.
Carte pour site web
<script src="https://mcp.tc/w/hookpulse.js" async></script>La carte apparaît à l’endroit de la balise. Ajoutez data-theme="dark" ou data-size="compact" à la balise pour la modifier. Le fichier contient tout ce qu’il lui faut : il ne fait aucune autre requête et ne dépose aucun 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>Utilisez-la sur les pages qui n’autorisent pas les scripts. Ajoutez ?theme=light ou ?theme=dark à l’adresse pour fixer les couleurs.
JSON
La fiche sous forme de données pour vos pages et vos outils : nom, accroche, URL du serveur, outils et liens « Add to ». N’importe quel site peut la lire (CORS ouvert).
https://mcp.tc/i/hookpulse.jsonPrompt pour l’IA
Collez-le dans un assistant de code IA, comme Claude Code ou Cursor, et il ajoutera la carte de HookPulse à votre site.
Ajoute à mon site la carte mcp.tc de HookPulse, un serveur MCP. C’est un seul script statique : pas de build, aucun paquet à installer, aucun cookie.
Place cette balise là où la carte doit apparaître. La carte s’affiche juste avant elle :
```html
<script src="https://mcp.tc/w/hookpulse.js" async></script>
```
Pour l’afficher ailleurs, mets ce conteneur à cet endroit et charge le même script une seule fois, par exemple avant `</body>`. Garde le lien à l’intérieur : les visiteurs sans JavaScript le voient.
```html
<div data-mcptc="hookpulse"><a href="https://mcp.tc/i/hookpulse">HookPulse on mcp.tc</a></div>
```
Options :
- `data-theme="light"` ou `"dark"` sur la balise ou le conteneur fixe les couleurs. Sans cela, la carte suit le mode clair ou sombre du visiteur.
- `data-size="compact"` donne une carte plus petite, sans l’accroche.
- La variable CSS `--mcptc-max-width` sur le conteneur ou un parent fixe la largeur (`520px` par défaut).
- `?lang=` dans l’URL du script choisit la langue de la carte : `en`, `it`, `fr`, `de` ou `es`.
Si le site a une Content Security Policy, autorise `script-src https://mcp.tc` et `img-src data:` (l’icône est intégrée).
Pour un README ou une autre doc en Markdown, utilise plutôt le badge :
```markdown
[](https://mcp.tc/i/hookpulse)
```
Référence : https://mcp.tc/fr/embedHistorique des changements
Nous lisons la liste d’outils de ce serveur toutes les 3 heures et notons ce qui change. Dernière lecture : 18 nov. 2026, 05:39 UTC.
-
1 outil retiré et 1 outil modifié.
Détails, 10 nov. 2026, 17:54 UTC
Retirés 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`).
Modifiés 1
pricingdescription et schéma d’entréeAvantCurrent publicprices andfree allowances; no charge.AprèsRead 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 outils modifiés.
Détails, 5 nov. 2026, 05:53 UTC
Modifiés 14
check_siteschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
create_siteschéma d’entréedelete_endpointschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
get_endpointschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
healthdescriptionAvantLiveness.AprèsRead service liveness before using HookPulse. Returns the health response; does not check a monitor.
import_crontabdescription et schéma d’entréeAvantReads 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.
AprèsReads 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 de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
ingest_keyschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
ingest_key_rotateschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
list_endpointsschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
list_eventsschéma d’entrée- Description de
guest_tokenAvantaucun
AprèsPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Description de
list_sitesping_slugstatus_feed_rotatestatus_feed_url -
Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 4 nov. 2026, 02:48 UTC
Instructions du serveur
AvantHookPulse 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.AprèsUse 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 outils modifiés.
Détails, 2 nov. 2026, 11:52 UTC
Modifiés 2
ping_slugschéma d’entréesignal_slugschéma d’entrée
-
2 outils modifiés.
Détails, 2 nov. 2026, 05:48 UTC
Modifiés 2
create_endpointdescription et schéma d’entréeAvantCreate 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.
AprèsCreate 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.
- Plus obligatoires :
guest_token - Description de
guest_tokenAvantaucun
AprèsExisting owner token, if available.
- Description de
alert_toAvantE-mail to alert on a miss; withoutit, the account isalerted.AprèsAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- Plus obligatoires :
create_sitedescription et schéma d’entréeAvantMonitor 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.
AprèsMonitor 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.
- Plus obligatoires :
guest_token - Description de
guest_tokenAvantaucun
AprèsExisting owner token, if available.
- Description de
alert_toAvantE-mail to alert on a miss; withoutit, the account isalerted.AprèsAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- Plus obligatoires :
-
3 outils modifiés. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 1er nov. 2026, 17:49 UTC
Modifiés 3
billingdescriptionAvantRead 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`).AprèsRead 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_endpointdescriptionAvantCreate 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`…AprèsCreate 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_sitedescriptionAvantMonitor 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…AprèsMonitor 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.
Instructions du serveur
AvantHookPulse 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.
AprèsHookPulse 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 outil modifié.
Détails, 31 oct. 2026, 14:50 UTC
Modifiés 1
cancel_plandescriptionAvantCancel 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.AprèsCancel 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 outils ajoutés et 8 outils modifiés. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 30 oct. 2026, 17:47 UTC
Ajoutés 6
billingLecture seuleRead 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_planÉcritureBuy 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_planÉcritureCancel 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_checkÉcritureChecks 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_plansLecture seuleThe 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`.
pricingLecture seuleCurrent public prices and free allowances; no charge.
Modifiés 8
contactdescription et schéma d’entréeAvantWrite 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.
AprèsWrite 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 de
pagamentoAvantaucun
Après`usdc`, `deposito` or `a_combinar`.
- Description de
create_endpointdescription et schéma d’entréeAvantCreate 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…AprèsCreate 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 de
interval_secAvantTolerated silence, in seconds.
AprèsTolerated silence, in seconds. Below the free minimum, it costs.
- Description de
create_sitedescriptionAvantMonitor 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…
AprèsMonitor 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_endpointdescriptionAvantStatus 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.
AprèsStatus 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_keydescriptionAvantReturns (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.
AprèsReturns (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_sitesdescriptionAvantThe state of every site you monitor (up, down, waiting, paused), with the last check.
AprèsThe 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_ingestdescriptionAvantSimulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
AprèsSimulates 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_slugdescriptionAvantCreate 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.
AprèsCreate 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.
Instructions du serveur
AvantHookPulse 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.
AprèsHookPulse 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.
-
Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 16 oct. 2026, 07:35 UTC
Instructions du serveur
AvantHookPulse 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.
AprèsHookPulse 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 outils ajoutés, 19 outils retirés et 1 outil modifié.
Détails, 16 oct. 2026, 01:35 UTC
Ajoutés 4
check_siteÉcritureCheck 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_siteÉcritureMonitor 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_sitesLecture seuleThe state of every site you monitor (up, down, waiting, paused), with the last check.
signal_slugLecture seuleSend 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.
Retirés 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.
Modifiés 1
create_endpointdescriptionAvantCreate 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.
AprèsCreate 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 outil modifié.
Détails, 15 oct. 2026, 16:40 UTC
Modifiés 1
contactLes 10 entrées les plus récentes montrent tous les détails ; les plus anciennes ne montrent que les noms.
-
5 outils retirés et 39 outils modifiés. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 15 oct. 2026, 04:32 UTC
Retirés 5
billingbuy_plancancel_planlist_planspricingModifiés 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_sluget 9 autresLes 10 entrées les plus récentes montrent tous les détails ; les plus anciennes ne montrent que les noms.
-
1 outil modifié.
Détails, 14 oct. 2026, 22:32 UTC
Modifiés 1
contactLes 10 entrées les plus récentes montrent tous les détails ; les plus anciennes ne montrent que les noms.
-
2 outils modifiés.
Détails, 14 oct. 2026, 16:35 UTC
Modifiés 2
buy_planlist_plansLes 10 entrées les plus récentes montrent tous les détails ; les plus anciennes ne montrent que les noms.
-
Début de l’observation : 44 outils.
FAQ
Puis-je coller mcp.tc/i/hookpulse dans mon client MCP ?
Non. Les liens mcp.tc sont des pages, pas des adresses de serveur. Connectez votre client à https://hookpulse.net/mcp, pour qu’il parle directement à HookPulse. Le lien rapide sert au partage : il ouvre cette page, avec les étapes de configuration pour chaque client.
HookPulse a-t-il besoin d’une clé API ou d’une connexion ?
Non. HookPulse ne demande ni compte ni clé.
HookPulse est-il un serveur distant ou local ?
Distant. HookPulse (WRP Consultoria e Informática) l’héberge à https://hookpulse.net/mcp, et il utilise Streamable HTTP. Il n’y a rien à installer.
Que peut faire HookPulse ?
Il a 29 outils, dont list_plans, buy_plan et cancel_plan. Vous pouvez créer des moniteurs avec une planification cron ou un intervalle de check-in fixe, importer une crontab et proposer un moniteur par ligne et signaler le démarrage, l’échec ou le code de sortie shell d’une exécution.
Quels clients peuvent l’utiliser ?
Tout client compatible avec les serveurs MCP distants : Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed et d’autres. Les étapes de configuration couvrent chacun d’eux.
mcp.tc suit-il les changements de HookPulse ?
Oui. L’onglet Historique de HookPulse montre chaque changement que nous trouvons dans ses outils, jusqu’aux descriptions et aux paramètres, ainsi que les nouvelles versions et les modifications de son propriétaire. Suivez la fiche pour recevoir un e-mail quand elle change.
Qui a rédigé cette page ?
Le robot de mcp.tc a lu les métadonnées de HookPulse (son handshake MCP, sa liste d’outils et ses pages publiques), et un modèle d’IA en a tiré le texte. Une personne examine tout ce que les vérifications ne peuvent pas confirmer. Le texte peut encore contenir des erreurs : si vous en repérez une, utilisez Signaler cette fiche sur cette page. Cette traduction a été réalisée par un modèle d’IA à partir du texte anglais.
mcp.tc n’est pas affilié à HookPulse (WRP Consultoria e Informática). Cette page a été construite à partir des métadonnées publiques de HookPulse, vérifiées pour la dernière fois le 18 nov. 2026, et un modèle d’IA a rédigé la description : elle peut contenir des erreurs. Les noms et marques appartiennent à leurs propriétaires. Quelque chose cloche ? Signaler cette fiche. La traduction a été réalisée par un modèle d’IA à partir du texte anglais.