Skip to main content
Glama
Jack-mi

vibelawyer

by Jack-mi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vibelawyer

No user-submitted related servers found.

    Related Servers

    • Anchor MCP

      salujajaskeerat
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to maintain durable, private, local memory by storing and linking records across collections, with structured review, search, and audit history.
      23
      MIT

    • mcp-legal-doc-analyzer

      dbsectrainer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local, on-device legal document analysis including clause extraction, risk flagging, compliance checking, and clause-level version comparison without sending documents externally.
      106 npm
      1
      MIT

    • Emsal MCP

      afsozer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables citation-safe legal research and document drafting over official Turkish case law and legislation, searching a local 11-million-decision corpus with full-text and semantic retrieval or querying live sources like Bedesten, AYM, Danıştay and mevzuat.gov.tr. It also supports citation verification, petition and bundle preparation, change reports, privacy redaction, and source health checks through core and loadable extended tool sets.
      3
      AGPL 3.0

    • Türk Hukuk AI MCP

      ahmetaliunaall-prog
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables local, privacy-conscious research across Turkish case law and legislation by searching precedent and statutes, retrieving decisions and article trees/content, and assembling sourced research drafts with verified quotations.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 25 tools

    Disambiguation3/5

    Most tools are clearly separated by document type, but get_case_status, get_workspace_summary, and get_review_progress all report overlapping progress/count information, creating real ambiguity. get_page_image and read_pages are well-distinguished, so the confusion is limited mainly to the status/progress cluster.

    Naming Consistency4/5

    Naming is predominantly verb_noun snake_case, e.g. list_volumes, record_party, validate_citations. Minor inconsistencies exist: set_case_basic vs. the record_* family, add_* vs. record_*, and a somewhat mixed use of list_/get_ for retrieval.

    Tool Count3/5

    25 tools is at the heavy end and includes at least three near-redundant status/progress tools. The many record_* tools are defensible because they map to distinct evidence and document categories, but the set would feel tighter with the status cluster consolidated.

    Completeness4/5

    The toolset covers the full review workflow: locating and reading volumes, registering parties/evidence/statements/transactions, validating citations, and exporting outputs. The main gaps are the absence of update/delete tools for correcting mis-registered records and no way to retrieve individual registered records, but these are workable gaps rather than blocking ones.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources