A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · uptybots/mcp-server · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository uptybots/mcp-server;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Connect AI assistants like **Claude**, **Cursor**, and other MCP-compatible tools to your UptyBots uptime monitors. What is this? An MCP (Model Context Protocol) server that gives AI assistants access to your UptyBots monitoring data. Ask your AI to check monitor status, review incidents, create new monitors, and more - through natural conversation. You probably want the hosted server instead There is now a remote server that needs no install and no API key: Add that URL to your client and it opens a browser for you to sign in and approve access. If you do not have an UptyBots account yet, you can create one at that step. With Claude Code: then run /mcp, pick **uptybots** and authenticate. **This package is the local alternative.** It runs on your own machine and authenticates with an API key instead of a browser sign-in - the right choice for MCP clients that cannot talk to remote servers, and for offline or self-contained setups. It exposes the same 15 tools and is not going away. Prerequisites - Node.js 18 or later - A UptyBots account - An API key from Account → API Keys Setup 1. Configure your AI client No install step needed: npx fetches the published package on first run. Add to your MCP client configuration: **Claude Desktop** (claude_desktop_config.json): **Claude Code** (~/.claude/settings.json) and **Cursor** (.cursor/mcp.json) use the same format. 2. Restart your AI client The MCP tools will be available immediately. Running from source (optional) To run a local checkout instead of the npm package: Then point the client at the checkout: Available Tools (15) Read | Tool | Description | |------|-------------| | list_monitors | List all monitors with filters (type, status) | | get_monitor | Get monitor details by ID | | get_incidents | Get downtime incidents for a monitor | | get_stats_hourly | Hourly performance stats | | get_stats_daily | Daily performance stats | | get_notifications | Notification history | Create | Tool | Description | |------|-------------| | create_http_monitor | Create HTTP/HTTPS monitor | | create_api_monitor | Create API endpoint monitor | | create_ping_monitor | Create ICMP ping monitor | | create_port_monitor | Create TCP port monitor | | create_ssl_monitor | Create SSL certificate monitor | | create_domain_monitor | Create domain expiration monitor | Manage | Tool | Description | |------|-------------| | pause_monitor | Pause a monitor | | resume_monitor | Resume a paused monitor | | delete_monitor | Delete a monitor | Prompts (5) Starting sentences an assistant can offer instead of asking you to phrase the request yourself. Each one is a wording of something the tools above already do; none adds capability. The hosted server offers exactly the same five. | Prompt | Argument | What it asks for |