LastPing MCP server
2026년 11월 12일 커밋AI 에이전트가 스스로 모니터링을 설정, 관리 및 읽기 하여 작업 실패, 중단 또는 사람의 승인이 필요한 상황을 알림으로 받을 수 있게 합니다.
다른 이름 lastping-dev/lastping-app, lastping-app
- 스타
- 3
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.2.2
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
LastPing MCP란?
LastPing은(는) MCP server입니다. AI 에이전트가 스스로 모니터링을 설정, 관리 및 읽기 하여 작업 실패, 중단 또는 사람의 승인이 필요한 상황을 알림으로 받을 수 있게 합니다.
프로젝트 README에서 생성된 요약
LastPing MCP server 정보
LastPing은 AI 에이전트, cron job 및 CI/CD 파이프라인을 위해 설계된 모니터링 시스템을 제공합니다. 에러를 감시하는 기존 모니터링 방식과 달리, 이 서비스는 프로세스가 체크인을 하지 않을 때 알림을 보내는 역방향 방식을 사용합니다. 이를 통해 작업이 중단되거나, 충돌하거나, 아예 시작되지 않더라도 신호의 부재를 통해 즉시 알림을 받을 수 있습니다. 시스템은 개인에게 무료로 제공되며 lastping.dev의 호스팅 서비스에 연결됩니다.
개발자는 MCP server를 사용하여 AI 에이전트가 스스로 모니터링 생명주기를 관리하도록 할 수 있습니다. 에이전트는 create_monitor 및 get_ping_instructions와 같은 도구를 사용하여 사람의 개입 없이 자체 알림을 설정할 수 있습니다. 이 서버는 확장을 통한 Claude Desktop 또는 mcp-remote 브릿지, 그리고 Claude Code를 위한 직접 연결 등 다양한 클라이언트 설정을 지원합니다. 또한 CLI wrapper를 제공하여 프로세스 생명주기, 종료 코드 및 OpenTelemetry 트레이스를 자동으로 보고합니다.
활용 사례
- 1자동화된 에이전트 모니터링 설정AI 에이전트가 독립적으로 모니터를 생성하고 상태 보고에 필요한 명령어를 가져올 수 있습니다.
- 2조용한 프로세스 실패 감지에러를 보고할 수 없는 고장 난 프로세스의 경우, 시스템이 신호를 보내지 못하는 상황을 식별하여 유용하게 활용할 수 있습니다.
- 3에이전트 실행 트레이스 관찰개발자는 CLI로 명령어를 래핑하여 OpenTelemetry 트레이스를 자동으로 내보내고 에이전트 성능을 추적할 수 있습니다.
- 4알림 대상 관리사용자는 제공되는 관리 도구를 사용하여 알림이 전송될 위치를 프로그래밍 방식으로 구성할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
LastPing MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 LastPing MCP 설치
$ claude mcp add --transport http lastping-app https://mcp.lastping.dev/mcpCursor에 LastPing MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"lastping-app": {
"url": "https://mcp.lastping.dev/mcp"
}
}
}VS Code에 LastPing MCP 설치
.vscode/mcp.json
{
"servers": {
"lastping-app": {
"type": "http",
"url": "https://mcp.lastping.dev/mcp"
}
}
}VS Code CLI에 LastPing MCP 설치
$ code --add-mcp '{"name":"lastping-app","type":"http","url":"https://mcp.lastping.dev/mcp"}'Codex에 LastPing MCP 설치
$ codex mcp add lastping-app --url https://mcp.lastping.dev/mcpCodex config.toml에 LastPing MCP 설치
~/.codex/config.toml
[mcp_servers.lastping-app] url = "https://mcp.lastping.dev/mcp"
Gemini CLI에 LastPing MCP 설치
$ gemini mcp add -s user --transport http lastping-app https://mcp.lastping.dev/mcpGemini settings.json에 LastPing MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"lastping-app": {
"url": "https://mcp.lastping.dev/mcp",
"type": "http"
}
}
}구성
LASTPING_AUTH
| 이름 | 설명 | 유형 |
|---|---|---|
| LASTPING_AUTH | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능lastping-dev/lastping-app is public and reachablegithub.com/lastping-dev/lastping-app ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/lastping-dev/lastping-app ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기LastPing 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 질문
LastPing MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http lastping-app https://mcp.lastping.dev/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
LastPing MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
LastPing은 무엇을 모니터링하나요?
AI 에이전트의 실패, 중단 또는 승인 요청뿐만 아니라 cron job 및 CI/CD 파이프라인을 모니터링합니다.
LastPing은 기존 모니터링과 어떻게 다른가요?
리소스의 상태를 감시하다가 문제가 생기면 보고하는 대신, LastPing은 체크인 신호를 기다리다가 신호가 수신되지 않으면 알림을 보냅니다.
개인이 LastPing을 사용하는 데 비용이 드나요?
네, 개인 사용자는 무료로 서비스를 이용할 수 있습니다.
기존 명령에 LastPing을 사용할 수 있나요?
네, LastPing CLI를 사용하여 모든 명령어를 래핑하고 시작 상태, 종료 코드 및 트레이스를 보고할 수 있습니다.