Notifario

io.notifarPublished by notifar.ioOfficial publisherv1.0.0Updated Oct 30, 2026

Website and server uptime monitoring from Russia and Europe: monitors, incidents, SSL, DNS.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint for Notifario uptime monitoring, letting an assistant work with website and server monitors, incidents, SSL and DNS checks.

What you can do
  • Work with uptime monitors for websites and servers, checked from Russia and Europe.
  • Review incidents and monitoring status.
  • Inspect SSL certificate and DNS check data.
  • No individual tools are listed in the manifest, so the exact actions available are not documented here.
When to use it
Useful when you want an assistant to look at uptime monitoring, incidents, or SSL and DNS checks for sites and servers alongside your other work, without switching to the Notifario dashboard.
Requirements
A remote MCP endpoint at notifar.io over streamable HTTP. OAuth authentication is required, so a Notifario account with access to the monitoring data is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Notifario account, so the assistant may see monitoring configuration and incident data. The manifest lists no tools, so whether it can create, change or delete monitors is unknown; review permissions before connecting.

Installation

In SourceWeft

  1. Open Notifario in the dashboard and add it to a workspace.
  2. Connect the required 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/io.notifar%2Fnotifario/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "notifario": {
      "type": "http",
      "url": "https://notifar.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

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