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
      C
      maintenance
      Enables local, on-device legal document analysis including clause extraction, risk flagging, compliance checking, and clause-level version comparison without sending documents externally.
      22 npm
      1
      MIT

    • document-evidence-mcp

      mtn888
      A
      license
      A
      quality
      B
      maintenance
      A local document evidence layer for MCP clients that ingests documents (PDF, Office, images) with optional OCR, indexes them in SQLite FTS, and provides retrieval tools with source coordinates.
      7
      MIT

    • Open Legal Chile

      elpabloultron
      A
      license
      B
      quality
      A
      maintenance
      Exposes 55 forensic tools over the Model Context Protocol so agents can query Chilean statutes, jurisprudence, administrative dicta and doctrine from official state sources such as BCN, PJUD, CGR and DT, while running locally for confidential casework. It also supports citation-validated drafting, deadline and docket monitoring, judgment deconstruction, OCR dossier compilation and legal knowledge-graph analysis for civil-law practice, teaching and research.
      74
      243 PyPI
      5
      Apache 2.0
    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources