Vivesca MCP Server
io.github.terry-li-hm/vivesca
local only
Vivesca runs on your own machine — the client starts it, so there is no endpoint to ping.
Opinionated MCP server — Pydantic output schemas, 7 domains, built to evolve.
The linked repository no longer exists on GitHub — it was deleted or made private.
—
Installs / week
not published
—
Stars
on GitHub
—
Last commit
from GitHub
—
License
language unknown
Vivesca — questions
Answers built from our own checks of this server.
Why is there no uptime for Vivesca?
Vivesca runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.
Is Vivesca still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.