LastPing is a remote MCP server that gives an AI agent 36 tools, among them add_incident_note, create_api_key, create_destination. It answers at https://mcp.lastping.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_incident_note | Requires an API key with the write scope or higher. Write back, in your own words, what you found out about an incident — so the person who gets paged reads a diagnosis instead of a timestamp: 'failed because the upstream API returned 503; Inputs: body, incident_id |
create_api_key | Requires an API key with the admin scope or higher. Create a new LastPing API key. The plaintext key is returned ONCE and cannot be retrieved again — store it immediately in a secret manager. Set expires_at for a short-lived key. Inputs: expires_at, name, scope |
create_destination | Requires an API key with the write scope or higher. Create a notification destination (channel) that monitors can route alerts to. Provide the fields for the chosen kind; unrelated fields are ignored. Non-email kinds are usable immediately; Inputs: address, bot_token, chat_id, kind, name, secret |
create_monitor | Requires an API key with the write scope or higher. Create a new LastPing monitor (or update an existing one if slug matches — returns 'updated' note on upsert). For heartbeat/ci monitors supply schedule_kind ('simple' requires period_s, 'c |
create_status_page | Requires an API key with the write scope or higher. Create a status page — a single page showing the current status and recent history of a chosen set of monitors. Reach for this when the health of a monitor needs to be visible to someone w Inputs: check_ids, slug, title, visibility |
declare_run_expectations | Requires an API key with the write scope or higher. Commit, at the START of a run, to the criteria by which THAT RUN will be judged when it closes — before you can see how it turns out. This is how a run stops grading itself: once declared, Inputs: assertions, check_id, rid |
delete_agent | Requires an API key with the write scope or higher. Permanently delete a LastPing agent from the registry by UUID. THIS DOES NOT DELETE ITS MONITORS: the agent_id foreign key on a monitor is ON DELETE SET NULL, so every monitor this agent o Inputs: id |
delete_destination | Requires an API key with the write scope or higher. Permanently delete a notification destination (channel). This cannot be undone. It also removes the destination from every monitor's routing — any event type routed ONLY to this destinatio Inputs: id |
delete_monitor | Requires an API key with the write scope or higher. Permanently delete a LastPing monitor by UUID. This cannot be undone. Inputs: id |
delete_status_page | Requires an API key with the write scope or higher. Permanently delete a status page. This cannot be undone, and any public URL it had stops working immediately. The monitors on the page are NOT affected — they keep running and alerting exa Inputs: id |
discover_monitors_reconcile | Requires an API key with the write scope or higher. Turn a scan of a repository or a host into monitors: send every scheduled job you found, get back a diff of what was created, what already existed and what has gone missing. This is how a Inputs: sources |
export_terraform | Requires an API key with the read scope or higher. Export existing LastPing monitors, destinations, routes, alert templates and status pages as Terraform HCL, including import blocks so they are adopted rather than recreated. Secrets are NO Inputs: include, monitor_slug, tag |
get_agent | Requires an API key with the read scope or higher. Get a single LastPing agent by UUID. Returns the same fields as list_agents, including its live status rollup. Use list_agents to find valid IDs, or register_agent to create one. Inputs: id |
get_alert_templates | Requires an API key with the read scope or higher. Get all custom alert message templates for a LastPing monitor. Returns a map of event-type (or event-type/cause) keys to template strings. Keys: 'down', 'recovery', 'fail', 'every-run', 'su Inputs: id |
get_monitor | Requires an API key with the read scope or higher. Get a single LastPing monitor by UUID. Returns the monitor's full configuration including its output assertions (the `assertions` field: conditions a successful run's ping body must satisfy Inputs: id |
get_ping_instructions | Requires an API key with the read scope or higher. Get everything needed to make a monitor actually report: the ping URL, copy-paste check-in snippets, and the three MECHANISMS for reporting, returned together. Call this right after create_ Inputs: id |
get_run_history | Requires an API key with the read scope or higher. Get structured run history for a monitor — both CI/CD runs and agent/heartbeat runs. Each run carries its run id (rid), kind, received_at, the progress steps reported under it (steps: seq, Inputs: id, limit |
list_agents | Requires an API key with the read scope or higher. List all agents registered in the project. Returns id, slug, name, status, monitor_count and last_seen for each. status is rolled up live from the monitors the agent owns, worst first: down |
list_api_keys | Requires an API key with the admin scope or higher. List all API keys in the project. Never returns plaintext key values — only the non-secret prefix, which is enough to identify a key for revoke_api_key. Each key includes last_used_at and |
list_destinations | Requires an API key with the read scope or higher. List all notification destinations (channels) in the project: email, webhook, Slack, Discord, Telegram. Use channel IDs to configure routing rules for monitors. |
list_incidents | Requires an API key with the read scope or higher. List recent incidents (downtime events) for a monitor. Returns newest first. An open incident has closed_at=null. Results are wrapped: `data` holds the list; `untrusted_fields` names the fi Inputs: id, limit |
list_monitors | Requires an API key with the read scope or higher. List all monitors in the authenticated LastPing project. Returns id, name, slug, status, ping_url for each. Use the tag param to filter by a single tag. Inputs: tag |
list_open_incidents | Requires an API key with the read scope or higher. Read this agent's failure inbox: every incident currently OPEN on the monitors it owns, newest first. Call it at the START of a run, before doing the work — this is how an agent finds out w Inputs: agent_id, limit |
list_status_pages | Requires an API key with the read scope or higher. List the project's status pages: id, slug, title, the monitors on each, visibility, and the public URL of any public page. A status page is how a monitor's health is shown to people who are |
pause_monitor | Requires an API key with the write scope or higher. Pause a LastPing monitor so it stops alerting (paused=true). The monitor still receives pings but does not alert. Inputs: id |
register_agent | Requires an API key with the write scope or higher. Register a new autonomous agent in the project's agent registry, returning its id, slug and wire-up instructions in one call — so an agent can go from nothing to reporting in a single conv Inputs: description, name |
resume_monitor | Requires an API key with the write scope or higher. Resume a paused LastPing monitor (paused=false). Alerting resumes on the next missed ping. Inputs: id |
revoke_api_key | Requires an API key with the admin scope or higher. Permanently revoke an API key AND every key it created, recursively: the keys that key made, the keys those keys made, all the way down. All of them stop authenticating immediately. Revoki Inputs: api_key_id |
set_alert_template | Requires an API key with the write scope or higher. Set or clear a single alert message template on a monitor. The template is validated for allowed variables before saving. Pass an empty string for template to reset that entry to the built Inputs: cause, event_type, id, template |
set_route | Requires an API key with the write scope or higher. Route a monitor's alerts for one event type to a set of destinations (channels). THIS REPLACES THE WHOLE SET for that event type — every destination you leave out stops receiving that even Inputs: channel_ids, event_type, monitor_id |
snooze_monitor | Requires an API key with the write scope or higher. Set or clear a maintenance window on a monitor. During the window the monitor will not alert. Provide exactly one of: duration (e.g. '1h', '24h'), until (RFC 3339 timestamp), or clear=true Inputs: clear, duration, id, until |
test_destination | Requires an API key with the write scope or higher. Send something through a destination right now, to move it from 'created' to 'known to work'. By default it delivers a synthetic 'LastPing test alert' immediately — use that after create_d Inputs: id, resend_verification |
update_agent | Requires an API key with the write scope or higher. Update an existing LastPing agent's name/description by UUID using merge-patch semantics: only the fields you supply are changed, and any field you omit keeps its current stored value. slu Inputs: description, id, name |
update_destination | Requires an API key with the write scope or higher. Update a notification destination's name and/or config in place. Only the fields you pass are changed. The destination kind cannot be changed — delete and recreate instead. Changing an ema Inputs: config, destination_id, name |
update_monitor | Requires an API key with the write scope or higher. Update an existing LastPing monitor's schedule/config by UUID using merge-patch semantics: only the fields you supply are changed, and any field you omit keeps its current stored value. If |
update_status_page | Requires an API key with the write scope or higher. Update a status page's title, slug, visibility, or the set of monitors on it. Only the arguments you pass are changed; anything you omit keeps its current value (this tool reads the page f Inputs: check_ids, id, slug, title, visibility |
Every block below points at https://mcp.lastping.dev/mcp. Pick your client and copy.
claude mcp add --transport http lastping https://mcp.lastping.dev/mcp
{
"mcpServers": {
"lastping": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.lastping.dev/mcp"]
}
}
}{
"mcpServers": {
"lastping": {
"url": "https://mcp.lastping.dev/mcp"
}
}
}{
"servers": {
"lastping": {
"type": "http",
"url": "https://mcp.lastping.dev/mcp"
}
}
}{
"context_servers": {
"lastping": {
"url": "https://mcp.lastping.dev/mcp"
}
}
}{
"mcpServers": {
"lastping": {
"serverUrl": "https://mcp.lastping.dev/mcp"
}
}
}{
"mcpServers": {
"lastping": {
"url": "https://mcp.lastping.dev/mcp"
}
}
}name: LastPing
version: 0.0.1
schema: v1
mcpServers:
- name: LastPing
type: streamable-http
url: https://mcp.lastping.dev/mcp{
"mcpServers": {
"lastping": {
"httpUrl": "https://mcp.lastping.dev/mcp"
}
}
}{
"mcpServers": {
"lastping": {
"type": "http",
"url": "https://mcp.lastping.dev/mcp"
}
}
}{
"mcpServers": {
"lastping": {
"url": "https://mcp.lastping.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.lastping.dev%2Fmcp&type=streamable_http&id=lastping&name=LastPing
It answered our last check on 19 October 2026 in 134 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by lastping.dev and served from mcp.lastping.dev, the vendor's own domain: https://mcp.lastping.dev/mcp.
36, as returned by the server's own tools/list on 11 September 2026: add_incident_note, create_api_key, create_destination, create_monitor, create_status_page, declare_run_expectations, delete_agent, delete_destination, and 28 more.
It answered our last check on 19 October 2026 in 134 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.lastping.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.lastping. Endpoint host: mcp.lastping.dev. ARD identifier: urn:air:dev.lastping:mcp:lastping.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.