Vivesca

io.github.terry-li-hmPublished by GitHub account terry-li-hmv0.2.2Updated Oct 24, 2026

Opinionated MCP server — Pydantic output schemas, 7 domains, built to evolve.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Vivesca is a local, opinionated MCP server with Pydantic output schemas spanning seven domains, designed to evolve over time.

What you can do
Vivesca is a local MCP server that exposes tools across seven domains, with responses shaped by Pydantic output schemas. The registry description calls it opinionated and built to evolve, suggesting a structured, schema-first design rather than a broad collection of ad hoc tools. No tool list, README, or usage details are provided, so the specific capabilities of each domain are not documented here.
When to use it
Consider it when you want a schema-validated MCP server covering several domains and are comfortable evaluating an early, evolving project. It is a poor fit if you need documented tools, a stable interface, or a clear list of what each domain does before installing.
Requirements
Runs as a local process over stdio, installed from the PyPI package vivesca, so a Python environment is needed. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Before you install
The manifest declares no authentication, environment variables, or headers, and no README is available. Because the tool list and behavior are undocumented, review the package before running it and confirm what data it reads or writes on your machine.

Installation

In SourceWeft

  1. Open Vivesca 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.2LatestSep 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.