An agent can connect on its own if it already holds UPTIME_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
n/a
stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package
Tool list unknown · checked 2026-10-19 10:20 UTC
Tool changes
No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
Service status / uptime MCP — Atlassian Statuspage v2.
Official server.json
{
"name": "me.yoping/uptime",
"title": "YoPingMe uptime monitoring",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://app.yoping.me/api/mcp",
"type": "streamable-http",
"headers": [
{
"name": "Authorization",
"isSecret": true,
"isRequired": true,
"description": "Bearer ypk_... - an API key with the 'mcp' scope, created on the YoPingMe Account page. Add the 'mcp:write' scope only if you want the assistant to be able to create monitors."
}
]
}
],
"version": "1.0.0",
"websiteUrl": "https://yoping.me/features/mcp",
"description": "Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks"
}