Vigilia

com.getvigiliaPublished by getvigilia.comOfficial publisherv1.0.0Updated Oct 27, 2026

Watches your live app, explains every problem in plain language and writes the fix prompt.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Vigilia monitors a live application, explains detected problems in plain language and drafts fix prompts for an assistant.

What you can do
  • The registry entry lists no individual tools, so capabilities are described only at a high level.
  • Watch a running app and surface problems as they occur
  • Explain each problem in plain language rather than raw error output
  • Write a fix prompt that can be handed to an AI assistant
When to use it
Consider it when you want an assistant to help triage issues in a deployed or running application and turn them into actionable fix requests, instead of reading logs and stack traces yourself.
Requirements
A remote MCP endpoint at app.getvigilia.com reached over streamable HTTP. OAuth sign-in is required; no environment variables or headers are declared. The app being watched presumably has to be connected to the service, though the input does not describe how.
Before you install
Access is granted through OAuth, so review which account and permissions you authorize. The service observes a live application, so it may receive runtime data, errors and possibly user-related information from that app; confirm what is sent to the vendor before connecting production systems. No tool list is published, so verify what actions it can take after signing in.

Installation

In SourceWeft

  1. Open Vigilia 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.getvigilia%2Fvigilia/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": {
    "vigilia": {
      "type": "http",
      "url": "https://app.getvigilia.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

1
  1. v1.0.0LatestOct 11, 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.