Skip to main content
Glama

Related Servers

Alternatives to aka-recht

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Lets 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.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to retrieve the verbatim text of German federal and state statutes, search official case law from BGH, BAG and BVerfG, and compute procedurally exact deadlines under §§ 187–193 BGB with weekend and public-holiday adjustment. It also supplies structured statutory-element blueprints with burden-of-proof allocation and assembles citation-secured research dossiers for pleadings.
      6
      MIT

    TDQS

    A3.6/5.0

    Scored across 36 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues