HookPulse
Servidor MCP de HookPulse (WRP Consultoria e Informática)
Supervisa tareas cron, copias de seguridad y automatizaciones con check-ins de dead-man, alertas de omisión y un feed de estado.
Conectar con HookPulse
No hace falta iniciar sesión. Conéctate con la URL propia de HookPulse:
Pégala en cualquier cliente compatible con servidores MCP remotos. Tu cliente habla directamente con HookPulse (WRP Consultoria e Informática), no a través de mcp.tc.
Compartir este servidor
El enlace abre esta página, con la URL y los pasos de configuración.
mcp.tc/i/hookpulseDescripción
HookPulse es un dead-man switch para rutinas programadas. Creas monitores con un intervalo o una programación cron, las rutinas hacen ping a una URL de ingesta y se dispara una alerta cuando los check-ins se detienen. Las herramientas también cubren señalar inicio, fallo y códigos de salida, importar un crontab, gestionar entradas y mediciones de colectores de dispositivos, un feed de estado, planes y facturación.
Funciona como un endpoint Streamable HTTP alojado en hookpulse.net/mcp. El endpoint responde a solicitudes anónimas sin iniciar sesión ni clave de API; los monitores están vinculados a un token de invitado o a una sesión de cuenta. Si se supera la cuota, devuelve una respuesta 402 con los detalles de pago x402 (USDC), y los planes de pago duran 30 días.
Qué puedes hacer
- Crear monitores con una programación cron o un intervalo fijo de check-in
- Importar un crontab y proponer un monitor por línea
- Señalar el inicio, el fallo o el código de salida de shell de una ejecución
- Listar monitores y leer los eventos de ping recientes
- Gestionar entornos de dispositivos y entradas de colectores
- Obtener un feed de estado público JSON/RSS de todos los monitores
- Ver los precios y comprar o cancelar un plan
Herramientas 29
list_plansSolo lecturaList plans
buy_planEscrituraBuy plan
cancel_planEscrituraCancel plan
api_indexSolo lecturaÍndice de la API
healthSolo lecturaEstado de salud
create_guestEscrituraCrear un token de invitado para acceder a tus monitores.
list_endpointsSolo lecturaListar los endpoints de monitor del invitado o de la sesión.
create_endpointEscrituraCrear un monitor con una programación cron o por intervalo.
create_siteEscrituraCrear sitio
check_siteEscrituraComprobar sitio
list_sitesSolo lecturaListar sitios
import_crontabEscrituraLeer un crontab y proponer un monitor por cada línea programada.
Mostrar 17 herramientas más
get_endpointSolo lecturaObtener el estado de un endpoint, incluida la próxima ejecución esperada.
delete_endpointPuede borrarEliminar el endpoint de un propietario.
list_eventsSolo lecturaListar los últimos pings de ingesta.
ping_ingestSolo lecturaSimular un check-in de cron en la URL de ingesta.
signal_startSolo lecturaRegistrar que una ejecución ha comenzado sin reiniciar el reloj de dead-man.
signal_failSolo lecturaRegistrar una ejecución fallida para que la siguiente comprobación envíe una alerta.
signal_exit_codeSolo lecturaEnviar un estado de salida de shell; 0 es un ping, de 1 a 255 un fallo.
ingest_keySolo lecturaObtener o generar la clave para crear monitores automáticamente en el primer ping.
ingest_key_rotatePuede borrarRotar la clave de ingesta para que la anterior no pueda crear monitores.
ping_slugSolo lecturaCrear un monitor en su primer check-in mediante un slug.
signal_slugSolo lecturaSeñalar slug
pricingSolo lecturaPricing
status_feed_urlSolo lecturaObtener la URL pública del feed de estado JSON/RSS de todos los endpoints.
status_feed_rotatePuede borrarRotar el token del feed de estado.
list_templatesSolo lecturaMostrar fragmentos de ingesta y los cuerpos JSON enviados ante una omisión.
contactEscrituraContacto
get_api_x402_checkEscrituraGet API X402 check
Leídas del servidor en funcionamiento el 18 nov 2026. Solo lectura, Escritura y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.
Prompts de ejemplo
Crea un monitor de HookPulse para mi copia de seguridad nocturna, esperada cada 24 horas.
Importa este crontab y propón un monitor para cada tarea.
Muestra los últimos eventos de ping de mi monitor de copias de seguridad.
Dame la URL del feed de estado de todos mis monitores.
Configuración
Todos los clientes se conectan a hookpulse.net. Elige el tuyo; la página recuerda tu elección.
Claude Code
- Ejecútalo en un terminal, en la carpeta de tu proyecto:
claude mcp add --transport http hookpulse https://hookpulse.net/mcp- Inicia Claude Code y escribe
/mcp. hookpulse debería aparecer como conectado.
Añade --scope user para que esté disponible en todos los proyectos, no solo en este.
Claude Desktop
- Abre Customize → Connectors, haz clic en + Add y luego en Add custom connector.
- Llámalo HookPulse y pega esta URL:
https://hookpulse.net/mcp- Haz clic en Add. Sus herramientas aparecen en el menú de herramientas del chat.
El archivo de configuración JSON de Claude Desktop solo inicia servidores locales. Los servidores remotos van por Connectors, y los conectores que añades en claude.ai también aparecen aquí.
claude.ai
- Abre el formulario de conectores en claude.ai. Este botón rellena el nombre y la URL por ti:
Añadir a claude.ai (se abre en una pestaña nueva)
- Comprueba que la URL es
https://hookpulse.net/mcpy haz clic en Add. - Actívalo en un chat desde el menú de herramientas.
Los planes gratuitos permiten un conector personalizado. En los planes Team y Enterprise lo añade un propietario en Organization settings → Connectors.
ChatGPT
- En chatgpt.com, ve a Plugins, selecciona + y luego Add custom MCP server.
- Escribe un nombre para el servidor.
- En Connection, pega
https://hookpulse.net/mcpcomo URL del servidor y luego, como autenticación, elige No authentication. - Marca I understand and want to continue y luego selecciona Create as a plugin.
Poder añadir un servidor MCP personalizado depende de tu plan de ChatGPT y de los permisos de tu espacio de trabajo (en los espacios Business pueden hacerlo los administradores y los propietarios).
Cursor
Añadir a Cursor (se abre en una pestaña nueva)
O añádelo a mano en ~/.cursor/mcp.json (todos los proyectos) o en .cursor/mcp.json (este proyecto):
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}VS Code
Instalar en VS Code (se abre en una pestaña nueva)
O desde un terminal:
code --add-mcp '{"name":"hookpulse","type":"http","url":"https://hookpulse.net/mcp"}'O haz commit del archivo en el repositorio como .vscode/mcp.json:
{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Devin Desktop
- Añádelo a
~/.config/devin/mcp_config.json(macOS y Linux) o a%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"hookpulse": {
"serverUrl": "https://hookpulse.net/mcp"
}
}
}- Actualiza la lista de servidores MCP en Cascade.
Devin Desktop es el nuevo nombre de Windsurf. Para los servidores remotos lee serverUrl (o url).
Codex
codex mcp add hookpulse --url https://hookpulse.net/mcpO edita directamente ~/.codex/config.toml:
[mcp_servers.hookpulse]
url = "https://hookpulse.net/mcp"Gemini CLI
gemini mcp add --transport http hookpulse https://hookpulse.net/mcpAsí lo añades al proyecto actual. Añade -s user para usarlo en todas partes.
Cualquier cliente
La mayoría de los clientes aceptan esta forma. Algunos llaman de otra manera al campo de la URL: serverUrl en Devin Desktop, httpUrl en el archivo de ajustes de Gemini CLI.
{
"mcpServers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}Zed pone los servidores bajo context_servers en sus ajustes. Cline necesita "type": "streamableHttp"; si no, supone SSE.
¿Tu cliente solo inicia servidores locales? Conéctalo con npx -y mcp-remote https://hookpulse.net/mcp.
Insertar
Muestra HookPulse en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones
La tarjeta, el iframe y el JSON están en inglés. Añade ?lang=it, fr, de o es a su dirección para otro idioma.
Insignia para 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>Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.
Tarjeta para web
<script src="https://mcp.tc/w/hookpulse.js" async></script>La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala 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>Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.
JSON
La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).
https://mcp.tc/i/hookpulse.jsonPrompt para la IA
Pégalo en un asistente de programación con IA, como Claude Code o Cursor, y añadirá la tarjeta de HookPulse a tu web.
Añade a mi web la tarjeta de mcp.tc de HookPulse, un servidor MCP. Es un solo script estático: sin paso de build, sin paquetes que instalar, sin cookies.
Pon esta etiqueta donde deba aparecer la tarjeta. La tarjeta se muestra justo antes de ella:
```html
<script src="https://mcp.tc/w/hookpulse.js" async></script>
```
Para mostrarla en otro sitio, pon allí este marcador y carga el mismo script una sola vez, por ejemplo antes de `</body>`. Deja el enlace dentro: lo ven los visitantes sin JavaScript.
```html
<div data-mcptc="hookpulse"><a href="https://mcp.tc/i/hookpulse">HookPulse on mcp.tc</a></div>
```
Opciones:
- `data-theme="light"` o `"dark"` en la etiqueta o el marcador fija los colores. Sin él, la tarjeta sigue el modo claro u oscuro del visitante.
- `data-size="compact"` da una tarjeta más pequeña, sin el eslogan.
- La variable CSS `--mcptc-max-width` en el marcador o en un elemento padre fija el ancho (por defecto `520px`).
- `?lang=` en la URL del script fija el idioma de la tarjeta: `en`, `it`, `fr`, `de` o `es`.
Si el sitio tiene una Content Security Policy, permite `script-src https://mcp.tc` e `img-src data:` (el icono va incrustado).
Para un README u otra documentación en Markdown, usa la insignia:
```markdown
[](https://mcp.tc/i/hookpulse)
```
Referencia: https://mcp.tc/es/embedHistorial de cambios
Leemos la lista de herramientas de este servidor cada 3 horas y registramos lo que cambia. Última lectura: 18 nov 2026, 05:39 UTC.
-
1 herramienta eliminada y 1 herramienta cambiada.
Detalles, 10 nov 2026, 17:54 UTC
Eliminadas 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`).
Cambiadas 1
pricingdescripción y esquema de entradaAntesCurrent publicprices andfree allowances; no charge.Despué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 herramientas cambiadas.
Detalles, 5 nov 2026, 05:53 UTC
Cambiadas 14
check_siteesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
create_siteesquema de entradadelete_endpointesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
get_endpointesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
healthdescripciónAntesLiveness.DespuésRead service liveness before using HookPulse. Returns the health response; does not check a monitor.
import_crontabdescripción y esquema de entradaAntesReads 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.
Despué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"…
- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
ingest_keyesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
ingest_key_rotateesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
list_endpointsesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
list_eventsesquema de entrada- Descripción de
guest_tokenAntesninguno
DespuésPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.
- Descripción de
list_sitesping_slugstatus_feed_rotatestatus_feed_url -
Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 4 nov 2026, 02:48 UTC
Instrucciones del servidor
AntesHookPulse 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.Despué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 herramientas cambiadas.
Detalles, 2 nov 2026, 11:52 UTC
Cambiadas 2
ping_slugesquema de entradasignal_slugesquema de entrada
-
2 herramientas cambiadas.
Detalles, 2 nov 2026, 05:48 UTC
Cambiadas 2
create_endpointdescripción y esquema de entradaAntesCreate 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.
Despué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.
- Ya no obligatorios:
guest_token - Descripción de
guest_tokenAntesninguno
DespuésExisting owner token, if available.
- Descripción de
alert_toAntesE-mail to alert on a miss; withoutit, the account isalerted.Despué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.
- Ya no obligatorios:
create_sitedescripción y esquema de entradaAntesMonitor 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.
Despué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.
- Ya no obligatorios:
guest_token - Descripción de
guest_tokenAntesninguno
DespuésExisting owner token, if available.
- Descripción de
alert_toAntesE-mail to alert on a miss; withoutit, the account isalerted.Despué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.
- Ya no obligatorios:
-
3 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 1 nov 2026, 17:49 UTC
Cambiadas 3
billingdescripciónAntesRead 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`).Despué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_endpointdescripciónAntesCreate 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`…Despué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_sitedescripciónAntesMonitor 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…Despué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.
Instrucciones del servidor
AntesHookPulse 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.
Despué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 herramienta cambiada.
Detalles, 31 oct 2026, 14:50 UTC
Cambiadas 1
cancel_plandescripciónAntesCancel 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.Despué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 herramientas añadidas y 8 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 30 oct 2026, 17:47 UTC
Añadidas 6
billingSolo lecturaRead 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_planEscrituraBuy 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_planEscrituraCancel 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_checkEscrituraChecks 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_plansSolo lecturaThe 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`.
pricingSolo lecturaCurrent public prices and free allowances; no charge.
Cambiadas 8
contactdescripción y esquema de entradaAntesWrite 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.
Despué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.
- Descripción de
pagamentoAntesninguno
Después`usdc`, `deposito` or `a_combinar`.
- Descripción de
create_endpointdescripción y esquema de entradaAntesCreate 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…Despué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`…
- Descripción de
interval_secAntesTolerated silence, in seconds.
DespuésTolerated silence, in seconds. Below the free minimum, it costs.
- Descripción de
create_sitedescripciónAntesMonitor 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…
Despué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_endpointdescripciónAntesStatus 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.
Despué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_keydescripciónAntesReturns (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.
Despué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_sitesdescripciónAntesThe state of every site you monitor (up, down, waiting, paused), with the last check.
Despué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_ingestdescripciónAntesSimulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
Despué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_slugdescripciónAntesCreate 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.
Despué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.
Instrucciones del servidor
AntesHookPulse 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.
Despué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.
-
Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 16 oct 2026, 07:35 UTC
Instrucciones del servidor
AntesHookPulse 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.
Despué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 herramientas añadidas, 19 herramientas eliminadas y 1 herramienta cambiada.
Detalles, 16 oct 2026, 01:35 UTC
Añadidas 4
check_siteEscrituraCheck 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_siteEscrituraMonitor 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_sitesSolo lecturaThe state of every site you monitor (up, down, waiting, paused), with the last check.
signal_slugSolo lecturaSend 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.
Eliminadas 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.
Cambiadas 1
create_endpointParte de esta entrada no se muestra, para que la página siga siendo ligera.
-
1 herramienta cambiada.
Detalles, 15 oct 2026, 16:40 UTC
Cambiadas 1
contactLas 10 entradas más recientes muestran todos los detalles; las anteriores, solo los nombres.
-
5 herramientas eliminadas y 39 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 15 oct 2026, 04:32 UTC
Eliminadas 5
billingbuy_plancancel_planlist_planspricingCambiadas 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_slugy 9 másLas 10 entradas más recientes muestran todos los detalles; las anteriores, solo los nombres.
-
1 herramienta cambiada.
Detalles, 14 oct 2026, 22:32 UTC
Cambiadas 1
contactLas 10 entradas más recientes muestran todos los detalles; las anteriores, solo los nombres.
-
2 herramientas cambiadas.
Detalles, 14 oct 2026, 16:35 UTC
Cambiadas 2
buy_planlist_plansLas 10 entradas más recientes muestran todos los detalles; las anteriores, solo los nombres.
-
Inicio del seguimiento: 44 herramientas.
Preguntas frecuentes
¿Puedo pegar mcp.tc/i/hookpulse en mi cliente MCP?
No. Los enlaces de mcp.tc son páginas, no direcciones de servidores. Conéctate con https://hookpulse.net/mcp, para que tu cliente hable directamente con HookPulse. El enlace rápido sirve para compartir: abre esta página, con los pasos de configuración para cada cliente.
¿HookPulse necesita una clave de API o iniciar sesión?
No. HookPulse no pide cuenta ni clave.
¿HookPulse es un servidor remoto o local?
Remoto. Lo aloja HookPulse (WRP Consultoria e Informática) en https://hookpulse.net/mcp, y usa Streamable HTTP. No hay nada que instalar.
¿Qué puede hacer HookPulse?
Tiene 29 herramientas, entre ellas list_plans, buy_plan y cancel_plan. Puedes crear monitores con una programación cron o un intervalo fijo de check-in, importar un crontab y proponer un monitor por línea y señalar el inicio, el fallo o el código de salida de shell de una ejecución.
¿Qué clientes pueden usarlo?
Cualquier cliente compatible con servidores MCP remotos: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed y otros. Los pasos de configuración cubren cada uno.
¿mcp.tc sigue los cambios de HookPulse?
Sí. La pestaña Historial de HookPulse muestra cada cambio que encontramos en sus herramientas, hasta las descripciones y los parámetros, además de las versiones nuevas y las ediciones de su responsable. Sigue la ficha para recibir un correo cuando cambie.
¿Quién escribió esta página?
El robot de mcp.tc leyó los metadatos propios de HookPulse (su handshake MCP, su lista de herramientas y sus páginas públicas), y un modelo de IA redactó el texto a partir de ellos. Una persona revisa todo lo que las comprobaciones no pueden confirmar. Aun así, el texto puede contener errores, así que si encuentras uno, usa Reportar esta ficha en esta página. Esta traducción la hizo un modelo de IA a partir del texto en inglés.
mcp.tc no tiene relación con HookPulse (WRP Consultoria e Informática). Esta página se creó a partir de los metadatos públicos de HookPulse, comprobados por última vez el 18 nov 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha. La traducción la hizo un modelo de IA a partir del texto en inglés.