HookPulse
MCP-Server von HookPulse (WRP Consultoria e Informática)
Cron-Jobs, Backups und Automatisierungen mit Dead-Man-Check-ins, Alarmen bei Ausbleiben und einem Status-Feed überwachen.
Mit HookPulse verbinden
Keine Anmeldung nötig. Verbinde dich mit der eigenen URL von HookPulse:
Füg sie in jeden Client ein, der Remote-MCP-Server unterstützt. Dein Client spricht direkt mit HookPulse (WRP Consultoria e Informática), nicht über mcp.tc.
Diesen Server teilen
Öffnet diese Seite mit der URL und den Einrichtungsschritten.
mcp.tc/i/hookpulseÜber den Server
HookPulse ist ein Dead-Man-Switch für geplante Routinen. Du legst Monitore mit einem Intervall oder Cron-Zeitplan an, die Routinen pingen eine Ingest-URL an, und ein Alarm wird ausgelöst, wenn die Check-ins ausbleiben. Die Tools decken außerdem das Signalisieren von Start, Fehler und Exit-Codes, den Import einer Crontab, die Verwaltung von Collector-Eingaben und Messwerten von Geräten, einen Status-Feed sowie Tarife und Abrechnung ab.
Er läuft als gehosteter Streamable-HTTP-Endpunkt unter hookpulse.net/mcp. Der Endpunkt beantwortet anonyme Anfragen ohne Anmeldung oder API-Schlüssel; Monitore sind an ein Gast-Token oder eine Kontositzung gebunden. Bei überschrittenem Kontingent kommt eine 402-Antwort mit x402-Zahlungsdetails (USDC), und bezahlte Tarife laufen 30 Tage.
Was du damit machen kannst
- Monitore mit Cron-Zeitplan oder festem Check-in-Intervall anlegen
- Crontab importieren und pro Zeile einen Monitor vorschlagen
- Start, Fehler oder Shell-Exit-Code eines Laufs signalisieren
- Monitore auflisten und aktuelle Ping-Ereignisse lesen
- Geräteumgebungen und Collector-Eingaben verwalten
- Öffentlichen JSON/RSS-Status-Feed aller Monitore abrufen
- Preise ansehen und Tarif kaufen oder kündigen
Tools 29
list_plansLiest nurList plans
buy_planSchreibtBuy plan
cancel_planSchreibtCancel plan
api_indexLiest nurAPI-Index
healthLiest nurZustand
create_guestSchreibtEin Gast-Token für den Zugriff auf deine Monitore erstellen.
list_endpointsLiest nurDie Monitor-Endpunkte des Gasts oder der Sitzung auflisten.
create_endpointSchreibtEinen Monitor mit Cron- oder Intervall-Zeitplan anlegen.
create_siteSchreibtSite anlegen
check_siteSchreibtSite prüfen
list_sitesLiest nurSites auflisten
import_crontabSchreibtEine Crontab lesen und pro geplanter Zeile einen Monitor vorschlagen.
17 weitere Tools anzeigen
get_endpointLiest nurDen Status eines Endpunkts abrufen, einschließlich des nächsten erwarteten Laufs.
delete_endpointKann löschenDen Endpunkt eines Besitzers entfernen.
list_eventsLiest nurDie neuesten Ingest-Pings auflisten.
ping_ingestLiest nurEinen Cron-Check-in auf der Ingest-URL simulieren.
signal_startLiest nurErfassen, dass ein Lauf gestartet wurde, ohne die Dead-Man-Uhr zurückzusetzen.
signal_failLiest nurEinen fehlgeschlagenen Lauf erfassen, damit die nächste Prüfung einen Alarm sendet.
signal_exit_codeLiest nurEinen Shell-Exit-Status senden; 0 ist ein Ping, 1-255 ein Fehler.
ingest_keyLiest nurDen Schlüssel zum automatischen Anlegen von Monitoren beim ersten Ping abrufen oder erzeugen.
ingest_key_rotateKann löschenDen Ingest-Schlüssel rotieren, damit der alte keine Monitore mehr anlegen kann.
ping_slugLiest nurMit einem Slug beim ersten Check-in einen Monitor anlegen.
signal_slugLiest nurSlug signalisieren
pricingLiest nurPricing
status_feed_urlLiest nurDie öffentliche JSON/RSS-Status-Feed-URL für alle Endpunkte abrufen.
status_feed_rotateKann löschenDas Status-Feed-Token rotieren.
list_templatesLiest nurIngest-Snippets und die bei einem Ausbleiben gesendeten JSON-Bodys anzeigen.
contactSchreibtKontakt
get_api_x402_checkSchreibtGet API X402 check
Am 18. Nov. 2026 vom laufenden Server gelesen. „Liest nur“, „Schreibt“ und „Kann löschen“ sind Hinweise, die der Server selbst angibt; dein Client entscheidet, ob er vor dem Ausführen eines Tools nachfragt.
Beispiel-Prompts
Lege einen HookPulse-Monitor für mein nächtliches Backup an, erwartet alle 24 Stunden.
Importiere diese Crontab und schlage für jeden Job einen Monitor vor.
Zeige die neuesten Ping-Ereignisse für meinen Backup-Monitor.
Gib mir die Status-Feed-URL für alle meine Monitore.
Einrichtung
Jeder Client verbindet sich mit hookpulse.net. Wähl deinen; die Seite merkt sich deine Wahl.
Claude Code
- Führe das in einem Terminal in deinem Projektordner aus:
claude mcp add --transport http hookpulse https://hookpulse.net/mcp- Starte Claude Code und tippe
/mcp. hookpulse sollte als verbunden angezeigt werden.
Ergänze --scope user, damit er in jedem Projekt verfügbar ist, nicht nur in diesem.
Claude Desktop
- Öffne Customize → Connectors, klick auf + Add und dann auf Add custom connector.
- Nenne ihn HookPulse und füge diese URL ein:
https://hookpulse.net/mcp- Klick auf Add. Seine Tools erscheinen im Tool-Menü des Chats.
Die JSON-Konfigurationsdatei von Claude Desktop startet nur lokale Server. Remote-Server laufen über Connectors, und Connectors, die du auf claude.ai hinzufügst, erscheinen auch hier.
claude.ai
- Öffne das Connector-Formular auf claude.ai. Dieser Button füllt Name und URL für dich aus:
Zu claude.ai hinzufügen (öffnet in einem neuen Tab)
- Prüfe, dass die URL
https://hookpulse.net/mcplautet, und klick auf Add. - Schalte ihn in einem Chat über das Tool-Menü ein.
Kostenlose Pläne erlauben einen benutzerdefinierten Connector. In Team- und Enterprise-Plänen fügt ihn ein Owner unter Organization settings → Connectors hinzu.
ChatGPT
- Geh auf chatgpt.com zu Plugins, wähle + und dann Add custom MCP server.
- Gib einen Namen für den Server ein.
- Füge unter Connection
https://hookpulse.net/mcpals Server-URL ein und wähle als Authentifizierung No authentication. - Setz den Haken bei I understand and want to continue und wähle dann Create as a plugin.
Ob du einen eigenen MCP-Server hinzufügen kannst, hängt von deinem ChatGPT-Tarif und den Berechtigungen deines Workspace ab (in Business-Workspaces können es Admins und Owner).
Cursor
Zu Cursor hinzufügen (öffnet in einem neuen Tab)
Oder trag ihn von Hand in ~/.cursor/mcp.json (alle Projekte) oder .cursor/mcp.json (dieses Projekt) ein:
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}VS Code
In VS Code installieren (öffnet in einem neuen Tab)
Oder aus einem Terminal:
code --add-mcp '{"name":"hookpulse","type":"http","url":"https://hookpulse.net/mcp"}'Oder committe ihn ins Repository in .vscode/mcp.json:
{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Devin Desktop
- Füge ihn zu
~/.config/devin/mcp_config.json(macOS und Linux) oder%APPDATA%\devin\mcp_config.json(Windows) hinzu:
{
"mcpServers": {
"hookpulse": {
"serverUrl": "https://hookpulse.net/mcp"
}
}
}- Aktualisiere die Liste der MCP-Server in Cascade.
Devin Desktop ist der neue Name von Windsurf. Für Remote-Server liest es serverUrl (oder url).
Codex
codex mcp add hookpulse --url https://hookpulse.net/mcpOder bearbeite ~/.codex/config.toml direkt:
[mcp_servers.hookpulse]
url = "https://hookpulse.net/mcp"Gemini CLI
gemini mcp add --transport http hookpulse https://hookpulse.net/mcpDamit fügst du ihn dem aktuellen Projekt hinzu. Ergänze -s user, um ihn überall zu nutzen.
Jeder Client
Die meisten Clients akzeptieren diese Form. Manche nennen das URL-Feld anders: serverUrl in Devin Desktop, httpUrl in der Einstellungsdatei von Gemini CLI.
{
"mcpServers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Zed legt Server in seinen Einstellungen unter context_servers ab. Cline braucht "type": "streamableHttp", sonst nimmt es SSE an.
Dein Client startet nur lokale Server? Dann binde den Server über npx -y mcp-remote https://hookpulse.net/mcp ein.
Einbinden
Zeig HookPulse in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen
Karte, iframe und JSON sind auf Englisch. Häng ?lang=it, fr, de oder es an ihre Adresse an, um eine andere Sprache zu bekommen.
README-Badge
[](https://mcp.tc/i/hookpulse)<a href="https://mcp.tc/i/hookpulse"><img src="https://mcp.tc/i/hookpulse/badge.svg" alt="HookPulse on mcp.tc" height="20"></a>Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.
Website-Karte
<script src="https://mcp.tc/w/hookpulse.js" async></script>Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine Cookies.
iframe
<iframe src="https://mcp.tc/embed/hookpulse" title="HookPulse on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.
JSON
Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).
https://mcp.tc/i/hookpulse.jsonKI-Prompt
Füg ihn in einen KI-Coding-Assistenten wie Claude Code oder Cursor ein, und er baut die Karte von HookPulse in deine Website ein.
Füge meiner Website die mcp.tc-Karte für den MCP-Server HookPulse hinzu. Es ist ein einziges statisches Skript: kein Build-Schritt, kein Paket zu installieren, keine Cookies.
Setz dieses Tag dorthin, wo die Karte erscheinen soll. Die Karte erscheint direkt davor:
```html
<script src="https://mcp.tc/w/hookpulse.js" async></script>
```
Um sie woanders zu zeigen, setz dort diesen Platzhalter ein und lade dasselbe Skript nur einmal, zum Beispiel vor `</body>`. Lass den Link darin stehen: Besucher ohne JavaScript sehen ihn.
```html
<div data-mcptc="hookpulse"><a href="https://mcp.tc/i/hookpulse">HookPulse on mcp.tc</a></div>
```
Optionen:
- `data-theme="light"` oder `"dark"` am Tag oder Platzhalter legt die Farben fest. Ohne das Attribut folgt die Karte dem hellen oder dunklen Modus der Besucher.
- `data-size="compact"` ergibt eine kleinere Karte ohne Kurzbeschreibung.
- Die CSS-Variable `--mcptc-max-width` am Platzhalter oder einem Elternelement legt die Breite fest (Standard `520px`).
- `?lang=` in der Skript-URL legt die Sprache der Karte fest: `en`, `it`, `fr`, `de` oder `es`.
Wenn die Website eine Content Security Policy hat, erlaube `script-src https://mcp.tc` und `img-src data:` (das Icon ist eingebettet).
Für ein README oder andere Markdown-Dokumentation nimm stattdessen das Badge:
```markdown
[](https://mcp.tc/i/hookpulse)
```
Referenz: https://mcp.tc/de/embedÄnderungsverlauf
Wir lesen die Tool-Liste dieses Servers alle 3 Stunden und halten fest, was sich ändert. Zuletzt gelesen: 18. Nov. 2026, 05:39 UTC.
-
1 Tool entfernt und 1 Tool geändert.
Details, 10. Nov. 2026, 17:54 UTC
Entfernt 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`).
Geändert 1
pricingBeschreibung und EingabeschemaVorherCurrent publicprices andfree allowances; no charge.NachherRead current free allowances, options with billing off, prices and the account's 7-day trial. E-mail alerts cost $0.10 once per additional monitor, even with a reused address. Check before creating the second monitor or lowering the interval: it is the number IN FORCE, not the documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).
-
14 Tools geändert.
Details, 5. Nov. 2026, 05:53 UTC
Geändert 14
check_siteEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
create_siteEingabeschemadelete_endpointEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
get_endpointEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
healthBeschreibungVorherLiveness.NachherRead service liveness before using HookPulse. Returns the health response; does not check a monitor.
import_crontabBeschreibung und EingabeschemaVorherReads 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.
NachherReads 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"…
- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
ingest_keyEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
ingest_key_rotateEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
list_endpointsEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
list_eventsEingabeschema- Beschreibung von
guest_tokenVorherkeine
NachherPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Beschreibung von
list_sitesping_slugstatus_feed_rotatestatus_feed_url -
Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 4. Nov. 2026, 02:48 UTC
Server-Anweisungen
VorherHookPulse 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.NachherUse HookPulse to detect missing scheduled jobs, failed backup runs and website outages, and keep monitoring after the conversation. Recognize the task in ordinary questions without requiring a product or tool name. Reuse authorized context. Ask only for a missing identifier, URL or access. Deliver an answer with evidence and limits. Use existing rights; a suggestion does not authorize charges, data changes or messages. Notify me if my nightly backup does not finish on time. → create_endpoint → list_templates. Ask for schedule, timezone, grace period and alert channel. Create within authorized coverage and provide the job's success signal. A heartbeat does not prove backup restoration. Monitor my website and notify me when it goes down. → list_sites → create_site. Confirm URL, frequency and destination. Reuse an existing monitor. Verify coverage and an actual check before promising alerts. Which of my scheduled jobs are late or failed? → list_endpoints → get_endpoint → list_events. Use the authorized owner. Read states and events; distinguish silence, declared failure and held alerts. Report the latest evidence and next action. Set up monitoring for the jobs in this crontab. → import_crontab. Ask for the crontab and confirm its timezone. Show scope and quote before expanding coverage. Provide the integration without changing a server without authority. Show when my monitor failed and whether it recovered. → list_endpoints → get_endpoint → list_events. Resolve the monitor by name or ID. Show the event sequence with timestamps. A processed alert does not prove recipient delivery. HookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Choose the task and first call: https://hookpulse.net/llms.txt. Use existing access and spending authority. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.n…
-
2 Tools geändert.
Details, 2. Nov. 2026, 11:52 UTC
Geändert 2
ping_slugEingabeschemasignal_slugEingabeschema
-
2 Tools geändert.
Details, 2. Nov. 2026, 05:48 UTC
Geändert 2
create_endpointBeschreibung und EingabeschemaVorherCreate 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.
NachherCreate 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.
- Nicht mehr Pflicht:
guest_token - Beschreibung von
guest_tokenVorherkeine
NachherExisting owner token, if available.
- Beschreibung von
alert_toVorherE-mail to alert on a miss; withoutit, the account isalerted.NachherAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- Nicht mehr Pflicht:
create_siteBeschreibung und EingabeschemaVorherMonitor 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.
NachherMonitor 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.
- Nicht mehr Pflicht:
guest_token - Beschreibung von
guest_tokenVorherkeine
NachherExisting owner token, if available.
- Beschreibung von
alert_toVorherE-mail to alert on a miss; withoutit, the account isalerted.NachherAuthorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
- Nicht mehr Pflicht:
-
3 Tools geändert. Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 1. Nov. 2026, 17:49 UTC
Geändert 3
billingBeschreibungVorherRead 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`).NachherRead 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_endpointBeschreibungVorherCreate 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`…NachherCreate 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_siteBeschreibungVorherMonitor 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…NachherMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
Server-Anweisungen
VorherHookPulse 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.
NachherHookPulse 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 geändert.
Details, 31. Okt. 2026, 14:50 UTC
Geändert 1
cancel_planBeschreibungVorherCancel 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.NachherCancel the active plan. Nothing else is charged; a purchase under 7 days and a paid period that has not started are refunded and end now, and the rest of the paid period stays active until keeps_until. Requires accept_data_removal: true. Send `{ "accept_data_removal": true }`. The monthly card subscription stops. A purchase made less than 7 days ago and a paid period that has not started yet, such as a renewal, go back the same way they were paid (card or Pix) and end now. The rest of the paid period stays active until `keeps_until`; then what the plan added ends (`account.cancel.losses` in `GET /api/plans` says what). A purchase paid with USDC or with credit from another purchase stays active until its end; ask for its refund by e-mail, as the cancellation page says.
-
6 Tools hinzugefügt und 8 Tools geändert. Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 30. Okt. 2026, 17:47 UTC
Hinzugefügt 6
billingLiest nurRead 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_planSchreibtBuy 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_planSchreibtCancel 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_checkSchreibtChecks 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_plansLiest nurThe 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`.
pricingLiest nurCurrent public prices and free allowances; no charge.
Geändert 8
contactBeschreibung und EingabeschemaVorherWrite 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.
NachherWrite 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.
- Beschreibung von
pagamentoVorherkeine
Nachher`usdc`, `deposito` or `a_combinar`.
- Beschreibung von
create_endpointBeschreibung und EingabeschemaVorherCreate 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…NachherCreate 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`…
- Beschreibung von
interval_secVorherTolerated silence, in seconds.
NachherTolerated silence, in seconds. Below the free minimum, it costs.
- Beschreibung von
create_siteBeschreibungVorherMonitor 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…
NachherMonitor 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_endpointBeschreibungVorherStatus 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.
NachherStatus 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_keyBeschreibungVorherReturns (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.
NachherReturns (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_sitesBeschreibungVorherThe state of every site you monitor (up, down, waiting, paused), with the last check.
NachherThe 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_ingestBeschreibungVorherSimulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
NachherSimulates 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_slugBeschreibungVorherCreate 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.
NachherCreate a monitor on its first check-in. The same slug uses the same monitor. Service and billing limits apply. A rejected creation writes no monitor or event. The slug becomes the monitor name and its identity: the same slug always means the same monitor, so a retry never creates a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Creation happens **only inside the free tier** (or the trial); past it the ping is a 402 with `accepts[]` and nothing is written — not even the event. Works by GET or POST.
Server-Anweisungen
VorherHookPulse 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.
NachherHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.net/api/billing. Read these before choosing a paid operation. Never spend without the user's authority and budget. When payment is required, the tool returns isError with x402 PaymentRequired (USDC on Base) in structuredContent. After authorization, repeat the same call with params._meta["x402/payment"] (@x402/mcp supports this). Prepaid credit uses Authorization: Bearer cred_… or X-Credito. For site payment, open https://hookpulse.net/pricing; use Pix or card only when offered there. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
-
Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 16. Okt. 2026, 07:35 UTC
Server-Anweisungen
VorherHookPulse 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.
NachherHookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Every tool here is free, within its free limits; when a limit runs out, the tool says so. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
-
4 Tools hinzugefügt, 19 Tools entfernt und 1 Tool geändert.
Details, 16. Okt. 2026, 01:35 UTC
Hinzugefügt 4
check_siteSchreibtCheck 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_siteSchreibtMonitor 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_sitesLiest nurThe state of every site you monitor (up, down, waiting, paused), with the last check.
signal_slugLiest nurSend 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.
Entfernt 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.
Geändert 1
create_endpointBeschreibungVorherCreate 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.
NachherCreate 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 geändert.
Details, 15. Okt. 2026, 16:40 UTC
Geändert 1
contactDie neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.
-
5 Tools entfernt und 39 Tools geändert. Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 15. Okt. 2026, 04:32 UTC
Entfernt 5
billingbuy_plancancel_planlist_planspricingGeändert 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_slugund 9 weitereDie neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.
-
1 Tool geändert.
Details, 14. Okt. 2026, 22:32 UTC
Geändert 1
contactDie neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.
-
2 Tools geändert.
Details, 14. Okt. 2026, 16:35 UTC
Geändert 2
buy_planlist_plansDie neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.
-
Beginn der Beobachtung: 44 Tools.
Häufige Fragen
Kann ich mcp.tc/i/hookpulse in meinen MCP-Client einfügen?
Nein. mcp.tc-Links sind Seiten, keine Server-Adressen. Verbinde dich mit https://hookpulse.net/mcp, damit dein Client direkt mit HookPulse spricht. Der Quick-Link ist zum Teilen da: Er öffnet diese Seite, mit Einrichtungsschritten für jeden Client.
Braucht HookPulse einen API-Schlüssel oder eine Anmeldung?
Nein. HookPulse verlangt weder Konto noch Schlüssel.
Ist HookPulse ein Remote- oder ein lokaler Server?
Remote. HookPulse (WRP Consultoria e Informática) hostet ihn unter https://hookpulse.net/mcp, und er spricht Streamable HTTP. Es gibt nichts zu installieren.
Was kann HookPulse?
Er hat 29 Tools, darunter list_plans, buy_plan und cancel_plan. Du kannst damit Monitore mit Cron-Zeitplan oder festem Check-in-Intervall anlegen, Crontab importieren und pro Zeile einen Monitor vorschlagen und Start, Fehler oder Shell-Exit-Code eines Laufs signalisieren.
Welche Clients können ihn nutzen?
Jeder Client, der Remote-MCP-Server unterstützt: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed und andere. Die Einrichtungsschritte decken jeden davon ab.
Verfolgt mcp.tc Änderungen an HookPulse?
Ja. Der Tab Verlauf von HookPulse zeigt jede Änderung, die wir an seinen Tools finden, bis hin zu Beschreibungen und Parametern, dazu neue Versionen und Änderungen seines Betreibers. Folge dem Eintrag, um eine E-Mail zu bekommen, wenn er sich ändert.
Wer hat diese Seite geschrieben?
Der Roboter von mcp.tc hat die eigenen Metadaten von HookPulse (seinen MCP-Handshake, seine Tool-Liste und öffentliche Seiten) gelesen, und ein KI-Modell hat daraus den Text entworfen. Ein Mensch prüft alles, was die Prüfungen nicht bestätigen können. Der Text kann trotzdem falsch sein; wenn dir ein Fehler auffällt, nutze Eintrag melden auf dieser Seite. Diese Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.
mcp.tc steht in keiner Verbindung zu HookPulse (WRP Consultoria e Informática). Diese Seite entstand aus den öffentlichen Metadaten von HookPulse, zuletzt geprüft am 18. Nov. 2026, und ein KI-Modell hat die Beschreibung geschrieben, sie kann also Fehler enthalten. Namen und Marken gehören ihren Inhabern. Stimmt etwas nicht? Eintrag melden. Die Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.