Developer · Remote MCP server
Monitoring
Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.pingvera/monitoring- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-23
- Updated
- 2026-07-23
- Publisher
- com.pingvera
- Namespace
- Namespace verified by the MCP Registry via the domain pingvera.com · how
- Website
- pingvera.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.pingvera.com/mcp | Authorization (required, 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; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Monitoring
Monitoring is a remote MCP server: there is nothing to install. Its endpoint is https://app.pingvera.com/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 (required, 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 |
|---|---|
| MonetLocal-first, state-centric memory for coding agents. MCP server + CLI. | Local · stdio |
| Mongo Scout MCPScout your MongoDB databases with AI - safety features, live monitoring, and data quality. | Local · stdio |
| MonitorBetterDB MCP server - Valkey observability for Claude Code and other MCP clients. | Local · stdio |
| MonitoringSite & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions. | Remote · HTTPLive check: sign-in required |
| MonitoringGoogle reviews API - fetch reviews from Google, Trustpilot, TripAdvisor, G2 + 50 platforms. | Remote · HTTPLive check: sign-in required |
| Monitoring AIopsGoverned SolarWinds Orion + PRTG + Zabbix ops: SWQL, alert rollup, health, 42 tools. | Local · stdio |
| Monte CarloData + AI observability - monitor and troubleshoot production-grade agents and the context they use. | Remote · HTTPLive check: sign-in required |
| MooringGit and GitHub operations - repo status, diffs, branches, PRs, issues, and Actions. | Local · stdio |