Developer · Remote MCP server
LastPing
Monitoring that agents set up for themselves: cron jobs, CI/CD pipelines and AI agent runs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.lastping/lastping- Version
- 0.2.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- dev.lastping
- Namespace
- Namespace verified by the MCP Registry via the domain lastping.dev · how
- Website
- lastping.dev/agents/
- Repository
- github.com/tp322d/lastping-app
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.lastping.dev/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect LastPing
LastPing is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.lastping.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| LandLens rental recordsOwner of record, code violations, evictions and tenant reviews for US college-town rentals. | Remote · HTTPLive check: ✓ handshake |
| Langchain MCPLangChain/LangGraph/DeepAgents knowledge + LangGraph agent debugging (Polly-like) | Local · stdio |
| Langfuse APILangfuse public API (Cloud and self-hosted): traces, prompts, datasets and gated writes. | Local · stdio |
| LastestRun visual regression tests, review diffs, and manage baselines on a Lastest instance. | Local · stdio |
| lastseen mortalityCheck whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned. | Local · stdio |
| LatchkeyTriage failing GitHub Actions jobs and see what self-heal repaired, in natural language. | Remote · HTTPLive check: sign-in required |
| LatentGateRead large logs, JSON and docs in a fraction of the tokens. Offline, fact-preserving optimizer. | Local · stdio |
| Latex MCPEnable AI agents to compile TeX files with LaTeX inside a Docker container. | Local · stdio |