# Pingvera MCP [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://pingvera.com  
**Views:** 7  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/monitoring-2

## Description
Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "pingvera-mcp": {
    "command": "npx",
    "args": ["-y","monitoring-2"]
  }
}
```

## Documentation

## What Pingvera MCP MCP server does

Pingvera MCP MCP server is described as a client-website monitoring service for agencies. Its scope covers four monitoring areas: uptime, incidents, SSL expiry, and domain expiry, along with server metrics. That makes it relevant to teams responsible for checking whether client websites are reachable, tracking service disruptions, and watching infrastructure-related indicators.

The available description does not identify individual MCP tools or explain whether the server reads monitoring data, creates or updates monitoring resources, sends notifications, or performs remediation. Those details should be confirmed from the project documentation before an agent workflow is designed around it.

## How it works

The available material establishes the monitoring subject and supported areas, but not the underlying implementation. It does not state whether Pingvera MCP MCP server connects to a hosted Pingvera account, polls websites directly, exposes an HTTP endpoint, or runs locally through a standard MCP transport. It also does not describe how websites, domains, certificates, incidents, or server metrics are selected and returned to an AI client.

A reasonable fit is an agency workflow in which an agent needs to work with monitoring information for client websites. The precise operations available to that agent remain unspecified, so avoid assuming that the server can acknowledge incidents, change checks, configure alerts, or access historical measurements.

## Setup and configuration

No README or installation instructions are available in the supplied material. There is no confirmed package name, executable command, endpoint, configuration file, environment variable, credential requirement, or client configuration example. As a result, no direct installation command can be provided safely.

Before using Pingvera MCP MCP server, confirm the official setup method at the source, including the required MCP transport, account or API credentials, monitored-site configuration, and any agency or client separation model. Also verify whether the service is hosted by Pingvera or must be deployed by the user.

## Tools and capabilities

The described capability set includes:

- Checking client-website uptime
- Working with incident monitoring
- Tracking SSL certificate expiry
- Tracking domain expiry
- Viewing or accessing server metrics

These are capability areas rather than confirmed tool names. The source does not provide schemas, parameters, return formats, alerting operations, or permissions for any MCP tools.

## Limitations and notes

The source provides only a short product description and no README. Supported MCP clients, authentication, pricing, license, transport, installation, and exact tool behavior are therefore unknown. The description identifies agencies as the target users but does not specify the number of websites supported, monitoring frequency, geographic coverage, retention period, notification channels, or server-metric types.

Use the Pingvera MCP MCP server listing as an initial fit check for agency website monitoring, not as a substitute for the provider's current technical documentation. Confirm operational and security requirements before giving an agent access to client monitoring data.

_Full upstream README: https://allmcps.com/mcp/monitoring-2/readme_