Hosted MCP server/Development

MonoDuty MCP server

Hosted at mcp.monoduty.com·Streamable HTTP

MonoDuty lets an assistant inspect monitoring coverage, propose configurations and create uptime monitors, job heartbeats and webhook sources with scoped permissions. It is described as HTTP transport with OAuth. The provider docs returned HTTP 522 on 16 November 2026, so the endpoint and auth flow could not be re-checked and are marked unverified.

Server unavailableThis MCP server isn't available right now. We couldn't connect to the published address when we checked on Nov 16, 2026, so installation is turned off. We've kept the listing for reference. Check the provider's documentation for a current address.Official docs
mcp.monoduty.com Streamable HTTP OAuth Source checked Nov 16, 2026 Server unavailable Reviewed 2026-11-16
About

Where it fits

Ops and platform teams that want uptime and heartbeat monitoring managed from an assistant.

  • Inspect monitoring coverage for a project.
  • Propose configurations for uptime monitors.
  • Create job heartbeats and webhook sources.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Connection

Endpoint and configuration

Endpoint
https://mcp.monoduty.com/mcp
Host
mcp.monoduty.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
monoduty
Listing type
Community or directory listing

The installer uses the server name monoduty. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that monoduty appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Inspect monitoring coverage for a project. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server unavailable

This MCP server isn't available right now. We couldn't connect to the published address when we checked on Nov 16, 2026, so installation is turned off. We've kept the listing for reference. Check the provider's documentation for a current address. The provider page does not currently load. This page stays online as a reference; check the provider's current page before setup.

Technical details

Cloudflare returned error 522 (connection timed out) for the docs and endpoint on 2026-11-16.

Provider page unavailable on Nov 16, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The provider's page did not load when we checked. Confirm the current setup steps before troubleshooting the client.
  • We couldn't reach the published address on the last check. Don't use the install command until the provider confirms a current address.
  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

MonoDuty documentationhttps://monoduty.com/docs/mcp