PagerDuty MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 Sep 2026.
Operate PagerDuty from your AI agent via MCP.
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
cacheFile := filepath.Join(c.cacheDir, c.cacheKey(path, params)+".json")
select {
case <-time.After(interval + jitter):
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Operate Resource Guru from your AI agent via MCP.
Open a Vivid Business account from your AI chat via MCP.
Operate a k3s / Kubernetes cluster from your AI agent — safe-by-default MCP server.
Manage GetIntel AI visibility (GEO) from your own AI agent.
Protect your AI agents and IDEs from malicious open-source packages.
Search thousands of MCP connectors from the AgentHotspot marketplace via your AI agent.
Generate images, GIFs, and PDFs from HTML, URLs, or templates — from your AI agent.
Persistent stateful remote SSH sessions for AI agents via MCP + OpenSSH.
Answers built from our own checks of this server.