Vesana

org.vesanaPublished by vesana.orgv1.909.0Updated Nov 7, 2026

Self-hosted infrastructure monitoring. Ask about problems, set up hosts, every AI action audited.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Vesana is a self-hosted infrastructure monitoring server that lets an assistant ask about problems, set up hosts, and keep every AI action audited.

What you can do
  • Ask about monitoring problems and current infrastructure state
  • Set up and configure hosts
  • Record and audit every action the assistant takes
  • Run as a self-hosted monitoring service reached over a remote HTTP endpoint
When to use it
Useful when you run your own monitoring stack and want an assistant to help investigate problems or onboard hosts, with an audit trail of what the AI did.
Requirements
A remote streamable HTTP endpoint at a Vesana address you host yourself; the manifest declares no authentication, environment variables, or headers.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to use it; secure the address before exposing it. The assistant can set up hosts and change monitoring configuration, and actions are audited, so review what it changes.

Installation

In SourceWeft

  1. Open Vesana 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.

Tools

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

Version history

1
  1. v1.909.0LatestNov 7, 2026

Score

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

    Publish an icon in the registry entry.

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