Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

org.vivesca/vivesca

PYPI · VIVESCA · SCANNED SEP 20

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

Available components

−15 this week 57 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 970 tokens (~34/item across 28 items; 24 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety94
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "keryx_draft_send" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the org.vivesca/vivesca MCP server?

org.vivesca/vivesca runs locally as a PyPI package, launched with uvx vivesca. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · vivesca

# add to Claude Code
claude mcp add org-vivesca-vivesca -- uvx vivesca
// .cursor/mcp.json
{
  "mcpServers": {
    "org-vivesca-vivesca": {
      "command": "uvx",
      "args": [
        "vivesca"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "org-vivesca-vivesca": {
      "command": "uvx",
      "args": [
        "vivesca"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add org-vivesca-vivesca -- uvx vivesca
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-vivesca-vivesca": {
      "type": "local",
      "command": [
        "uvx",
        "vivesca"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add org-vivesca-vivesca --command uvx --arg vivesca
# ~/.hermes/config.yaml
mcp_servers:
  org-vivesca-vivesca:
    command: "uvx"
    args: ["vivesca"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "org-vivesca-vivesca": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "vivesca"
      ]
    }
  }
}
# add to Vellum
assistant mcp add org-vivesca-vivesca -t stdio -c uvx -a vivesca
// mcp.json
{
  "mcpServers": {
    "org-vivesca-vivesca": {
      "command": "uvx",
      "args": [
        "vivesca"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
  • 18 Sept 26 −14
    • Malware scan: pass → unverified security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +12
    • Malware scan: unverified → pass security
    • Stability: pass → 0.77 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/vivesca@0.2.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 18 packages
Packages resolved 18
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 24 exposed · ~846 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
deltos_send_image ~33

Send an image to Telegram with optional caption.

NameTypeReqDescription
captionstring
pathstringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

deltos_send_text ~40

Send text to Telegram. HTML by default; format='plain' for raw.

NameTypeReqDescription
formatstring
textstringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

fasti_create_event ~70

Create a calendar event. Date: YYYY-MM-DD. Time: 24h HH:MM.

NameTypeReqDescription
datestringyes
description
from_timestringyes
location
summarystringyes
to_timestringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

fasti_delete_event ~33

Delete an event. event_id from fasti_list_events — never guess.

NameTypeReqDescription
event_idstringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

fasti_list_events ~34

List calendar events for a date (HKT). Call first to get event IDs.

NameTypeReqDescription
datestring
NameTypeReqDescription
eventsstringyes

No examples provided.

fasti_move_event ~48

Reschedule an event. event_id from fasti_list_events — never guess.

NameTypeReqDescription
datestringyes
event_idstringyes
timestringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

keryx_draft_send ~42

Draft a WhatsApp message. NEVER sends — returns shell block for manual execution.

NameTypeReqDescription
messagestringyes
namestringyes
NameTypeReqDescription
draftstringyes

No examples provided.

keryx_list_chats ~25

List recent WhatsApp chats.

NameTypeReqDescription
limitinteger
NameTypeReqDescription
chatsstringyes

No examples provided.

keryx_read_messages ~41

Read a WhatsApp conversation. Merges phone + LID JID threads.

NameTypeReqDescription
limitinteger
namestringyes
NameTypeReqDescription
messagesstringyes

No examples provided.

keryx_sync_status ~20

Check the wacli sync daemon status.

Input schema present but exposes no named parameters.

NameTypeReqDescription
detailsobject
messagestringyes
statusstringyes

No examples provided.

navigator_check_auth ~28

Check browser auth for a domain. Detects login redirects.

NameTypeReqDescription
domainstringyes
NameTypeReqDescription
authenticatedboolean
domainstringyes
fixstring
messagestring
urlstring

No examples provided.

navigator_extract ~36

Extract page content from URL. Structured output with automated fallbacks.

NameTypeReqDescription
urlstringyes
wait_msinteger
NameTypeReqDescription
errorstring
methodstring
successboolean
textstring
titlestring
urlstringyes

No examples provided.

navigator_screenshot ~45

Screenshot a URL. Wakes display, handles nav fallbacks.

NameTypeReqDescription
output_pathstring
urlstringyes
wait_msinteger
NameTypeReqDescription
dataobject
messagestringyes
pathstringyes
successbooleanyes
urlstringyes

No examples provided.

noesis_ask ~31

Thorough web search (~$0.01). Structured survey with citations.

NameTypeReqDescription
querystringyes
NameTypeReqDescription
synthesisstringyes

No examples provided.

noesis_research ~39

Deep research (~$0.40). EXPENSIVE — depth must justify cost. Saves to ~/docs/.

NameTypeReqDescription
querystringyes
NameTypeReqDescription
synthesisstringyes

No examples provided.

noesis_search ~33

Quick web search (~$0.006). Cited synthesis for factual lookups.

NameTypeReqDescription
querystringyes
NameTypeReqDescription
synthesisstringyes

No examples provided.

oghma_add ~35

Add a memory manually.

NameTypeReqDescription
categorystring
confidencenumber
contentstringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

oghma_search ~59

Search memories: keyword/vector/hybrid. Use for past session recall.

NameTypeReqDescription
categorystring
limitinteger
modestring
querystringyes
source_toolstring
NameTypeReqDescription
resultsstringyes

No examples provided.

oghma_stats ~19

Memory DB stats: counts by category and source.

Input schema present but exposes no named parameters.

NameTypeReqDescription
statsstringyes

No examples provided.

oghma_status ~20

Memory DB status: path, count, daemon state.

Input schema present but exposes no named parameters.

NameTypeReqDescription
detailsobject
messagestringyes
statusstringyes

No examples provided.

vigilis_check_readiness ~18

Oura readiness + exercise recommendation.

Input schema present but exposes no named parameters.

NameTypeReqDescription
guidancestringyes
summarystringyes

No examples provided.

vigilis_check_sleep ~35

Oura sleep data. 'today' for last night, 'week' for trend.

NameTypeReqDescription
periodstring
NameTypeReqDescription
summarystringyes

No examples provided.

vigilis_check_system ~22

System health: lucerna, budget, recent copia events.

Input schema present but exposes no named parameters.

NameTypeReqDescription
sectionsarrayyes

No examples provided.

vigilis_log_symptom ~40

Log a symptom to vault health log.

NameTypeReqDescription
notesstring
severitystring
symptomstringyes
NameTypeReqDescription
dataobject
messagestringyes
successbooleanyes

No examples provided.

Common questions

What is the org.vivesca/vivesca MCP server?

org.vivesca/vivesca is an MCP server listed in the public MCP registry as org.vivesca/vivesca. Opinionated MCP server, Pydantic output schemas, 7 domains, built to evolve. This page covers its PyPI package (vivesca).

Is the org.vivesca/vivesca MCP server safe to use?

org.vivesca/vivesca scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the org.vivesca/vivesca MCP server expose?

org.vivesca/vivesca exposes 24 tools: deltos_send_image, deltos_send_text, fasti_create_event, fasti_delete_event, fasti_list_events, and 19 more. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.

Is the org.vivesca/vivesca MCP server still maintained?

org.vivesca/vivesca is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.