Developer · Remote MCP server
YoPingMe uptime monitoring
Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
me.yoping/uptime- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-22
- Updated
- 2026-08-22
- Publisher
- me.yoping
- Namespace
- Namespace verified by the MCP Registry via the domain yoping.me · how
- Website
- yoping.me/features/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.yoping.me/api/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
- Checked on
- 2026-10-05
How to connect YoPingMe uptime monitoring
YoPingMe uptime monitoring is a remote MCP server: there is nothing to install. Its endpoint is https://app.yoping.me/api/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 |
|---|---|
| Yaw Labs AWS MCPAWS MCP server - call any AWS API from AI assistants, with first-class SSO re-login. | Local · stdio |
| Ybe CheckYbe Check - security and compliance orchestrator for AI-generated repositories. | Local · stdio |
| YggdrasilOne shared, durable memory for your AI coding agents - local-first, zero-dependency. | Local · stdio |
| YocoolabPin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent. | Local · stdio |
| Yotta Verify MCPPre-install security scanner for AI agent skills (local stdio MCP). Offline static scan; no upload. | Local · stdio |
| YTDL RMCPYt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI. | Local · stdio |
| YTDL RMCPRust MCP server and CLI for yt-dlp search, downloads, metadata, transfers, and Plex playlists. | Local · stdio |
| Yuque MCPYuque MCP server with safe read/write tools for groups, group members, repositories, docs, and TOC. | Local · stdio |