Opservo

com.getopservoPublished by getopservo.comOfficial publisherv1.2.0Updated Oct 24, 2026

Read-only server insight: why a Linux server or K8s cluster is slow, failing or changed.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

A remote, read-only MCP server that helps an assistant investigate why a Linux server or Kubernetes cluster is slow, failing or has changed.

What you can do
Investigate server and cluster health: read-only insight into why a Linux server or Kubernetes cluster is slow, failing or has changed. The manifest lists no individual tools, so the exact operations are not documented here. Access is scoped to an Opservo workspace, authenticated by OAuth sign-in or a workspace API token.
When to use it
Useful when you want an assistant to help diagnose performance problems, failures or unexpected changes on Linux servers or Kubernetes clusters without giving it write access.
Requirements
A remote endpoint at api.getopservo.com over streamable HTTP. An Opservo account and workspace are needed; authentication is OAuth (required) or an Authorization header carrying a workspace API token. No local runtime or packages.
Before you install
The Authorization header carries a secret workspace API token, so treat it as sensitive. The server is described as read-only, but it exposes insight into your servers and clusters to the assistant and to Opservo as the remote provider; confirm what data leaves your environment before connecting.

Installation

In SourceWeft

  1. Open Opservo 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/com.getopservo%2Fopservo/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": {
    "opservo": {
      "type": "http",
      "url": "https://api.getopservo.com/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

3
  1. v1.2.0LatestOct 16, 2026
  2. v1.1.1Oct 15, 2026
  3. v1.1.0Oct 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.