ExpiryOwl

com.expiryowlPublished by expiryowl.comOfficial publisherv1.0.0Updated Oct 26, 2026

SSL certificate, domain expiry, DNS and uptime monitoring for web agencies, grouped by client.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote ExpiryOwl MCP server that lets an assistant check SSL certificate, domain expiry, DNS and uptime monitoring data grouped by client.

What you can do
  • No tool list is published, so capabilities come from the description: the server exposes ExpiryOwl's monitoring data for web agencies.
  • Review SSL certificate and domain expiry status.
  • Inspect DNS and uptime monitoring results.
  • View monitoring grouped by client.
When to use it
Useful for web agencies or freelancers who already track client websites in ExpiryOwl and want an assistant to look up certificate, domain, DNS or uptime status while working in chat.
Requirements
A remote MCP endpoint at expiryowl.com over streamable HTTP. Requires an ExpiryOwl account and an API key created under Integrations > API keys, sent as an Authorization bearer header. Network access to the endpoint.
Before you install
The API key is a live credential sent in the Authorization header; keep it out of shared logs and transcripts. The published description does not state whether tools only read data or can also change monitoring settings, so confirm before relying on it for write actions.

Installation

In SourceWeft

  1. Open ExpiryOwl in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/com.expiryowl%2Fexpiryowl/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "expiryowl": {
      "type": "http",
      "url": "https://expiryowl.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 26, 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.