aka-recht
Related Servers
Alternatives to aka-recht
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceLets an MCP client list and manage local purchases, receipts, and confirmed return, refund, or warranty deadlines through eight tools that reuse the same business logic and SQLite data as the web app. It runs over local stdio, so CRUD works without the HTTP backend, though reminder processing still needs it.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables assistants to file, search, and manage invoices, contracts, policies, and official letters, and to create, explain, update, and remind on their derived deadlines. It also supports mail scanning, warranty checks, notification testing, settings changes, and upkeep through a running local paperwork app.MIT
- FlicenseNot gradedqualityDmaintenanceA database-first personal knowledge management system powered by a local MCP server, providing 29 tools to manage and search structured knowledge (meetings, emails, people, accounts, projects, todos, etc.) via a single SQLite file.-
- AlicenseNot gradedqualityBmaintenanceEnables offline management of sales contracts, customer receipts, traceable earnings accruals, actual payouts, and personal finance forecasts through a local stdio interface.MIT
- AlicenseAqualityCmaintenanceEnables append-only maintenance of a legal developments tracker stored as CSV, with duplicate checks, dry-run proposals, fingerprint-safe appends, digest views, and transparent candidate scoring.6MIT
- AlicenseAqualityBmaintenanceEnables searching and reading full texts of anonymised Czech court decisions from the Ministry of Justice public database, with filters by court, legal keywords, statutory provision, judge and dates, plus lookup by case number or ECLI and browsing by publication date. Decisions can be exported as DOCX/TXT and cached locally in SQLite with diacritic-insensitive full-text search.11MIT
TDQS
Scored across 36 tools
Most tools map cleanly to distinct entity+action pairs (e.g. *_anlegen vs *_setzen vs *_eintragen are consistently create/update/append). However the document-handling cluster (bestand_pruefen vs bestand_abgleichen, dokument_ordnen vs dokument_verschieben vs datei_ablegen) and frist_berechnen/eintragen/setzen require careful reading to distinguish, since several touch the same file/inventory concepts.
Dominant, predictable German entity_verb pattern (fall_anlegen, verfahren_setzen, aufgabe_setzen, frist_eintragen, ereignis_setzen), which is easy to scan. Minor deviations (texterkennung, fall_uebersicht, dokument_text, quellen_katalog, sicherung_probe) use noun_noun instead, but not enough to break predictability.
At 36 tools the set is heavy and on the borderline-to-excessive side by count. The domain (case management with cases, participants, proceedings, deadlines, events, drafts, documents, backups, OCR) is genuinely broad, so most tools earn their place, but the surface is large and would benefit from consolidation.
Coverage is deep across the case lifecycle: create/list/overview for cases, plus participants, proceedings, tasks, deadlines, events, notes, drafts, documents, sources, journal, OCR, and backup/restore. The main gap is the absence of delete/remove operations anywhere (likely intentional for an archival legal record), but otherwise there are no obvious dead ends.