Zuzia

app.zuzia.myPublished by my.zuzia.appOfficial publisherv0.1.0Updated Nov 1, 2026

Monitor servers and websites with Zuzia: hosts, uptime, metrics, alerts, logs, services and tasks.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Zuzia is a remote MCP server that lets an assistant monitor servers and websites: hosts, uptime, metrics, alerts, logs, services and tasks.

What you can do
  • Monitor hosts and websites, including uptime and server metrics
  • Review alerts, logs, services and tasks
  • Work with the monitoring data through a hosted Zuzia endpoint rather than local tooling
  • No individual tools are listed in the manifest, so exact actions depend on the account's Zuzia setup
When to use it
Useful when you want an assistant to look at Zuzia monitoring data — uptime, metrics, alerts, logs, services and tasks — while investigating incidents or checking the health of hosts and websites.
Requirements
A remote MCP endpoint at my.zuzia.app over streamable HTTP. A Zuzia API key sent as a Bearer token in the Authorization header. A paid Zuzia plan with MCP access enabled in the account settings.
Before you install
The API key is a secret sent in the Authorization header; keep it out of shared logs and prompts. MCP access requires a paid plan. The manifest lists no tools, so confirm what the connected account can read or change before relying on it.

Installation

In SourceWeft

  1. Open Zuzia 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/app.zuzia.my%2Fmcp/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": {
    "zuzia": {
      "type": "http",
      "url": "https://my.zuzia.app/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. v0.1.0LatestNov 1, 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.