Notification Cadence Guide

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.0.7Updated Oct 8, 2026

Set notification cadence for an operations workflow

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server for setting the notification cadence of an operations workflow.

What you can do
The registry entry describes a single purpose: setting notification cadence for an operations workflow. No tools are listed, so the exact operations an assistant can call are not documented. It runs as a remote endpoint rather than a local package.
When to use it
Consider it only if you run an operations workflow and want an assistant to adjust how often its notifications are sent. With no tool list or documentation, confirm what it actually changes before relying on it.
Requirements
A remote MCP client that can connect to a streamable HTTP endpoint. No authentication, environment variables or headers are declared, and no local runtime or package is needed.
Before you install
The server is described as setting notification cadence, which likely changes notification settings in a workflow; verify what it modifies and whether changes can be undone. No authentication is declared, so anyone who can reach the endpoint may be able to use it. The endpoint is a temporary-looking tunnel host, which may not be stable.

Installation

In SourceWeft

  1. Open Notification Cadence Guide in the dashboard and add it to a workspace.
  2. 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/io.github.Wxt-ai%2Fnotification-cadence-guide/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": {
    "notification-cadence-guide": {
      "type": "http",
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/notification-cadence-guide"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.7LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.