com.vigotime/tools
com.vigotime/tools · 1.0.0
Free German workforce calculators (bridge days, net working time, staffing/PeBeM) - no auth needed.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.vigotime.comstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 6 tools.
- Protocol
- 2025-06-18
- Calls itself
- vigotime-public 1.0.0
- Handshake time
- 538 ms
- HTTP status
- 200
The tools it lists (6, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
calculate_bridge_daysBerechnet die effizientesten Brückentage für ein Jahr (2026–2030) und ein deutsches Bundesland: welche Urlaubstage ergeben die längsten zusammenhängenden Frei-Blöcke. Deterministische Rechnung auf Basis der gesetzlichen Feiertage — keine KI-Schätzung. Interaktive Version: https://vigotime.com/de/tools/brueckentage-rechner
compare_bridge_day_yearsVergleicht die Jahre 2026–2030 für ein Bundesland: welches Jahr eignet sich am besten für Brückentage (Score aus der Feiertagslage, offengelegte Formel, rein regelbasiert).
calculate_net_working_timeBerechnet die tatsächlich verfügbare Netto-Arbeitszeit einer Vollzeitkraft pro Jahr: Bruttoarbeitstage minus Urlaub, Krankheit, Fortbildung und Feiertage — als Tage, Stunden und Quote, optional als Team-Summe. Interaktive Version: https://vigotime.com/de/tools/nettoarbeitszeit-rechner
calculate_shift_staffingBerechnet den Personalbedarf (VZÄ) eines Schichtbetriebs: jährlich zu besetzende Stunden geteilt durch die Netto-Jahresarbeitszeit einer Vollzeitkraft (Brutto minus Urlaub, Feiertage, Fortbildung), multipliziert mit dem Ausfallfaktor 1/(1 − Ausfallquote). Der krankheitsbedingte Ausfall fließt ausschließlich über die Ausfallquote ein — genau einmal. Reine Arithmetik nach offengelegter Formel. Interaktive Version: https://vigotime.com/de/tools/personalbedarf-pflege
calculate_care_staffing_pebemBerechnet den PeBeM-VZÄ-Höchstwert einer Pflegeeinrichtung aus der Bewohnerstruktur (Anzahl Bewohner je Pflegegrad 1–5) nach § 113c SGB XI — aufgeschlüsselt nach Qualifikationsniveau (Fachkraft, Hilfskraft mit/ohne Ausbildung).
get_vigotime_infoKurzprofil von vigotime: regelbasierte, automatische Dienstplanung mit Wunschsystem, Urlaubsverwaltung und Zeiterfassung für Schichtbetriebe (Pflege, Klinik, Labor, Gastronomie, Produktion u. a.). Liefert Produktüberblick, die wichtigsten Links und den Weg zum vollwertigen Produkt-MCP (Dienstpläne per Tool-Call rechnen lassen).
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.vigotime/tools, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 52 days ago. The registry entry · vigotime.com