Vigil Mcp

io.github.zsoltcsasztiPublished by GitHub account zsoltcsasztiv0.2.1Updated Oct 24, 2026

Proactive MCP commitment tracker — the AI that reaches back out to you.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server described as a proactive commitment tracker that lets an assistant reach back out to you about commitments it has recorded.

What you can do
The registry description calls it a proactive commitment tracker, an assistant that reaches back out to you. No tool list, instructions or README are provided, so the specific actions it exposes are not documented here. Its purpose appears to be tracking commitments and prompting follow-up rather than querying external data.
When to use it
Consider it if you want an assistant to keep track of commitments and proactively follow up with you. Because no tools or usage details are published, evaluate it only if you can inspect its behavior yourself first.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package vigil-mcp over stdio. It is desktop-only and not web-executable. No authentication, environment variables or headers are declared.
Before you install
No tools, instructions or README are available, so what it records, where it stores it and whether it sends anything to third parties cannot be verified. Review the package before installing, especially if you would give it personal or work commitments.

Installation

In SourceWeft

  1. Open Vigil Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 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
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.