Oh Dear
app.ohdearPublished by ohdear.appOfficial publisherv1.0.0Updated Oct 24, 2026
Website monitoring: uptime, SSL certificates, broken links, DNS, cron jobs and status pages.
Overview
Lets an assistant read Oh Dear website monitoring data such as uptime, SSL certificates, broken links, DNS, cron jobs and status pages.
- What you can do
- This remote MCP server connects an assistant to Oh Dear, a website monitoring service. According to the registry description, it covers uptime checks, SSL certificates, broken links, DNS, cron jobs and status pages. The manifest does not list individual tools, so the exact set of operations is not documented here.
- When to use it
- Useful when you want an assistant to look up the health of monitored websites, for example checking uptime or certificate status, reviewing broken links or DNS records, or inspecting cron job and status page information during an incident or routine review. It is not intended for changing site content or for general web search.
- Requirements
- A remote MCP endpoint at reached over streamable HTTP. OAuth authentication is required, so the user needs an Oh Dear account and must complete the authorization flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Oh Dear in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.ohdear%2Fohdear/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"oh-dear": {
"type": "http",
"url": "https://ohdear.app/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 14, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
