LastPing MCP server
Commit 12. Nov. 2026Ermöglicht es einem AI Agent, sein eigenes Monitoring aufzusetzen, zu verwalten und auszulesen, um bei Fehlern, Stillstand oder Bedarf an menschlicher Freigabe zu alarmieren.
Auch bekannt als lastping-dev/lastping-app, lastping-app
- Stars
- 3
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.2.2
- Letzter Commit
- 12. Nov. 2026
- Lizenz
- MIT
Was ist LastPing MCP?
LastPing ist ein MCP server. Ermöglicht es einem AI Agent, sein eigenes Monitoring aufzusetzen, zu verwalten und auszulesen, um bei Fehlern, Stillstand oder Bedarf an menschlicher Freigabe zu alarmieren.
Zusammenfassung generiert aus dem README des Projekts
Über LastPing MCP server
LastPing bietet ein Monitoring-System, das speziell für AI Agents, Cron Jobs und CI/CD Pipelines entwickelt wurde. Im Gegensatz zum traditionellen Monitoring, das auf Fehler wartet, nutzt dieser Service einen invertierten Ansatz: Er alarmiert dich, wenn ein Prozess kein Check-in sendet. So wird sichergestellt, dass du benachrichtigt wirst, wenn eine Aufgabe stagniert, abstürzt oder gar nicht erst startet, da das Signal ausbleibt. Das System ist für Einzelpersonen kostenlos und verbindet sich mit einem gehosteten Service unter lastping.dev.
Entwickler können den MCP server nutzen, um AI Agents zu ermöglichen, ihren eigenen Monitoring-Lifecycle zu verwalten. Ein Agent kann Tools wie create_monitor und get_ping_instructions verwenden, um seine eigenen Alerts ohne menschliches Eingreifen einzurichten. Der Server unterstützt verschiedene Client-Setups, einschließlich Claude Desktop über eine Extension oder die mcp-remote Bridge sowie direkte Verbindungen für Claude Code. Zudem bietet er einen CLI Wrapper, um Prozess-Lifecycles, Exit Codes und OpenTelemetry Traces automatisch zu melden.
Was du damit machen kannst
- 1Automatisierte Einrichtung des Agent-MonitoringsEin AI Agent kann eigenständig seine eigenen Monitore erstellen und die notwendigen Commands abrufen, um seinen Status zu melden.
- 2Erkennung von silent process failuresDas System erkennt, wenn ein Job kein Signal sendet, was besonders nützlich für defekte Prozesse ist, die selbst keine Fehler melden können.
- 3Beobachtung von Agent Execution TracesEntwickler können das CLI nutzen, um Commands zu wrappen und OpenTelemetry Traces automatisch zu exportieren, um die Performance des Agents zu tracken.
- 4Verwaltung von Alert-ZielenNutzer können programmatisch konfigurieren, wohin Alerts gesendet werden, indem sie die verfügbaren Management-Tools nutzen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du LastPing MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenLastPing MCP in Claude Code installieren
$ claude mcp add --transport http lastping-app https://mcp.lastping.dev/mcpLastPing MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"lastping-app": {
"url": "https://mcp.lastping.dev/mcp"
}
}
}LastPing MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"lastping-app": {
"type": "http",
"url": "https://mcp.lastping.dev/mcp"
}
}
}LastPing MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"lastping-app","type":"http","url":"https://mcp.lastping.dev/mcp"}'LastPing MCP in Codex installieren
$ codex mcp add lastping-app --url https://mcp.lastping.dev/mcpLastPing MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.lastping-app] url = "https://mcp.lastping.dev/mcp"
LastPing MCP in Gemini CLI installieren
$ gemini mcp add -s user --transport http lastping-app https://mcp.lastping.dev/mcpLastPing MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"lastping-app": {
"url": "https://mcp.lastping.dev/mcp",
"type": "http"
}
}
}Konfiguration
LASTPING_AUTH
| Name | Beschreibung | Typ |
|---|---|---|
| LASTPING_AUTH | — |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarlastping-dev/lastping-app is public and reachablegithub.com/lastping-dev/lastping-app ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-12github.com/lastping-dev/lastping-app ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeHTTPS endpoint answered 401 (sign-in required)Bestanden
README
Auf GitHub ansehenLastPing alerts you when your AI agents fail, stall, wait for your approval or never start, and watches the cron jobs and CI/CD pipelines around them. Free for individuals.
Most monitoring watches a thing and tells you when it looks wrong. LastPing waits for a thing to check in and tells you when it doesn't. That inversion is the whole product: a job that breaks can't send you an error, but it can fail to send you anything, and absence is the one signal a broken process can still produce.
This repository holds the client pieces: the lastping CLI, which wraps
any command and reports its start, exit code and traces, and the MCP server,
which lets an AI agent set up and read its own monitoring. The hosted service
they talk to is at lastping.dev, free for
individuals.
Quick start
# 1. Install the CLI (macOS and Linux, amd64 and arm64)
curl -fsSL https://raw.githubusercontent.com/lastping-dev/lastping-app/main/install.sh | sh
# 2. Wrap a job: a start ping, your command untouched, then its exit code
lastping run --monitor <monitor-id> -- ./backup.sh
# 3. Or give your AI assistant the hosted MCP server, and sign in
https://mcp.lastping.dev/mcp
Create the monitor, and get its id, at app.lastping.dev, or let your assistant do it over MCP. Connect steps for each client are at lastping.dev/mcp/.
Install
curl -fsSL https://raw.githubusercontent.com/lastping-dev/lastping-app/main/install.sh | sh
No Go toolchain needed — that pulls a prebuilt binary for macOS and Linux, on amd64 and arm64, and verifies its checksum. Windows builds are on the releases page.
If you do have Go:
go install github.com/lastping-dev/lastping-app/cmd/lastping@latest
lastping run — reporting you can't forget
Put it in front of whatever you already run:
lastping run --monitor <monitor-id> -- python nightly_etl.py
lastping run --monitor <monitor-id> -- ./backup.sh
lastping run --monitor <monitor-id> -- claude
It sends a start ping, runs your command untouched, and reports the exit code when it finishes — success on 0, failure on anything else, with the tail of stderr attached so the alert says why.
Three properties worth knowing, because they are the difference between a monitoring wrapper you can trust in production and one you remove after a bad night:
- Your exit code always propagates. The wrapper exits with whatever your command exited with, so CI behaves exactly as it did before you added it.
- A failed ping never touches your command. If LastPing is unreachable, your job still runs, still writes its output, still exits normally.
- Interactive stays interactive. stdin and stdout are handed over as file descriptors, so wrapping a REPL or an agent session works.
Why a wrapper rather than an instruction? Because anything advisory decays. An
AI agent told to report on every task will stop doing it, and a cron line you
meant to add a curl to never gets it. A wrapper reports from the process
lifecycle, so nothing depends on anybody remembering.
Traces
lastping run always configures your wrapped command's OpenTelemetry
exporter, in its environment only, so an auto-instrumented agent can export
its own trace spans with no code change:
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT— the header-free monitor-URL form (<ping url>/v1/traces) whenLASTPING_API_KEYis not set, so a headerless exporter can still authenticate; the ping host's/v1/traces(the Bearer form) when it is set.OTEL_RESOURCE_ATTRIBUTES—lastping.monitor_id=<id>,lastping.run_id=<rid>appended to whatever you already set, so a trace's spans join the same run the surrounding pings report.OTEL_EXPORTER_OTLP_HEADERS—Authorization=Bearer <your key>, only whenLASTPING_API_KEYis set and you have not already set that variable yourself.
Any of the three you already set is left alone. The key is never used to authenticate a ping; the ping URL stays unauthenticated by design, as above.
MCP server — let an agent set up its own monitoring
Claude Desktop extension
A one-click install for Claude Desktop on macOS and Windows that keeps your key in the system keychain. It needs no Node.js.
- Download lastping.mcpb.
- Double-click it; Claude Desktop opens its install dialog.
- Paste a write-scope key from Settings, API keys at app.lastping.dev.
The extension runs this repository's stdio binary (below) on your computer.
It is built by mcpb/build.sh when a version is tagged, and every release is
signed; the release build fails rather than ship an unsigned bundle. The
certificate is self-signed, so Claude Desktop shows the extension as
unverified. The signature still proves the bundle came from this repository's
release pipeline and was not altered after it was signed. A local build of
mcpb/build.sh without the signing secrets is unsigned and says so.
MCPB_CERT_CA_ISSUED is kept for a future certificate from a public CA.
Claude Desktop through the mcp-remote bridge
Claude Desktop's config file runs local programs only, so LastPing connects
through the mcp-remote bridge. Add this to claude_desktop_config.json
(macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):
{
"mcpServers": {
"lastping": {
"command": "/ABSOLUTE/PATH/TO/npx",
"args": [
"-y", "mcp-remote",
"https://mcp.lastping.dev/mcp",
"--header", "Authorization:${LASTPING_AUTH}"
],
"env": {
"PATH": "/FOLDER/THAT/HOLDS/npx:/usr/bin:/bin",
"LASTPING_AUTH": "Bearer lp_your_key"
}
}
}
}
- Needs Node.js. Claude Desktop does not read your shell's PATH, so give it
the full path: run
which npxin a terminal and put the result incommand(with nvm it looks like/Users/you/.nvm/versions/node/v22.11.0/bin/npx), and its folder at the front ofPATHinenv. - Quit and reopen Claude Desktop; it reads the file only at start-up. Settings, Connectors then lists lastping.
- Without a key, add LastPing as a custom connector instead (Customize,
Connectors, Add custom connector, then paste
https://mcp.lastping.dev/mcp) and sign in to LastPing in the browser. The same connector covers claude.ai, the Claude mobile apps and Cowork.
Other clients
Claude Code connects directly, no bridge:
claude mcp add --transport http --scope user lastping https://mcp.lastping.dev/mcp --header "Authorization: Bearer <key>".
Cursor, Windsurf, Codex CLI, Gemini CLI and other clients:
lastping.dev/mcp/#connect.
The hosted server is the recommended path, and it always carries the current tool set. Most clients connect by adding the URL and signing in to LastPing, with nothing to install; Cursor and Windsurf use the URL and an API key. With a key, Claude Desktop connects through the extension or the mcp-remote bridge above.
A stdio binary is also here if you would rather run it yourself:
go install github.com/lastping-dev/lastping-app/cmd/lastping-mcp@latest
Monitors: create_monitor · get_monitor · list_monitors ·
update_monitor · delete_monitor · pause_monitor · resume_monitor ·
snooze_monitor
Discovery: discover_monitors_reconcile
Reporting: get_ping_instructions · declare_run_expectations
Incidents & runs: list_incidents · get_run_history · get_run
(one run's full timeline, assertion verdicts and spans) · list_runs
(runs across every monitor, traced runs included, with filters) ·
get_incident (one incident's recorded timeline)
Tracing: get_trace_setup (the set-up steps for one tool, from the server) ·
create_ingest_key (a tracing key bound to one monitor; a write key is
enough) · get_trace_diagnostics (why a sent span was refused)
Agent observability: get_agent_dependencies · get_agent_usage ·
list_dependencies · list_discovered_agents · adopt_discovered_agent
The failure loop: list_open_incidents · add_incident_note
Alert routing: set_route · delete_route
Delivery log: list_deliveries, recent alert deliveries across every
monitor, no paging
Destinations: list_destinations · create_destination ·
update_destination · test_destination · delete_destination
Alert templates: get_alert_templates · set_alert_template
Agent registry: register_agent · list_agents · get_agent ·
update_agent · delete_agent
Status pages: list_status_pages · create_status_page ·
update_status_page · delete_status_page
API keys: create_api_key (optional scope: read / write / admin / ingest) ·
list_api_keys · regenerate_api_key (new secret, same key; does not
cascade) · revoke_api_key (cascades to every key it created)
Terraform: export_terraform
This binary carries the same tool set as the hosted server at
mcp.lastping.dev. It is a thin REST client throughout: every tool is a
direct HTTP call to the management API, so it stays free to run yourself with
no lag behind the hosted surface beyond a new release.
The one that matters most is get_ping_instructions: an agent calls
create_monitor, then asks for its own ping commands, and wires them into its
own work — in one conversation, without a human opening a dashboard.
Ping API
Every monitor gets a URL. There is nothing to install and no library to keep current; anything that can make an HTTP request can report.
| What happened | Request |
|---|---|
| finished successfully | POST <ping-url> |
| started a run | POST <ping-url>/start |
| failed | POST <ping-url>/fail with the error as the body |
| exited with a code | POST <ping-url>/<exit-code> |
| waiting on a human | POST <ping-url>/blocked |
| progress worth recording | POST <ping-url>/note |
Add ?rid=<id> to pair a run's start with its result, so LastPing can group a
run's pings and time it.
# The classic one-liner, at the end of a cron job:
curl -fsS -m 10 --retry 3 https://ping.lastping.dev/<monitor-id>
Traces
POST https://ping.lastping.dev/v1/traces accepts an OTLP/HTTP export
(application/x-protobuf or application/json, gzip accepted) with a
Bearer key (an ingest key bound to the monitor, from create_ingest_key;
a write or admin key also works), or POST <ping-url>/v1/traces for exporters that
cannot set headers. Spans need the resource attribute lastping.monitor_id;
with lastping.run_id they join that run, and without it each trace becomes a
run of its own. A payload is capped at 1 MiB decompressed,
500 spans per request and 2,000 spans per run. lastping run sets all of
this up for you — see Traces above.
Monitoring as code
resource "lastping_monitor" "nightly_etl" {
name = "nightly-etl"
slug = "nightly-etl"
schedule_kind = "cron"
cron_expr = "0 3 * * *"
tz = "Europe/Berlin"
grace_s = 900
}
The provider is on the
Terraform Registry
as lastping-dev/lastping, with source at
lastping-dev/terraform-provider-lastping.
Links
- lastping.dev — the hosted service, free for individuals
- AI agent monitoring — the agent-first guide
- MCP server — connect configs per client
- Terraform provider — monitoring as code
- Integration guides — cron, Kubernetes, systemd, GitHub Actions, Python, Node
License
MIT. See LICENSE.
LastPing MCP Fragen
Wie füge ich LastPing MCP zu Claude Code hinzu?
Führe claude mcp add --transport http lastping-app https://mcp.lastping.dev/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich LastPing MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Was überwacht LastPing?
Es überwacht AI Agents auf Fehler, Stillstand oder Anfragen nach Freigaben sowie Cron Jobs und CI/CD Pipelines.
Wie unterscheidet sich LastPing von traditionellem Monitoring?
Anstatt eine Ressource zu beobachten und zu melden, wenn etwas falsch aussieht, wartet LastPing auf ein Check-in und schlägt Alarm, wenn keines erfolgt.
Fallen für Einzelpersonen Kosten für die Nutzung von LastPing an?
Nein, der Service ist für Einzelpersonen kostenlos.
Kann ich LastPing mit meinen bestehenden Commands nutzen?
Ja, du kannst das LastPing CLI nutzen, um jeden Command zu wrappen, damit Startzeitpunkt, Exit Code und Traces gemeldet werden.