Skip to main content
Glama
Sign In
michigan-law-mcp

michigan-law-mcp

by michnaugh1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to michigan-law-mcp

No user-submitted related servers found.

    Related Servers

    • North Dakota Century Code

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pull the full text of any state statute by citation, and to search official section catchlines by topic or keyword to find matching citations. Keyless, and handles citation suffixes such as "12.1-16-01" or "47-16-13.1".
      397 npm
      MIT

    • local-notebook

      rita112025-cpu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to query a locally imported collection of PDF, TXT, and MD files via SQLite FTS5 full-text search (including Chinese), and to browse notebooks, source files, and individual passages. Every search result carries traceable citations such as filename, page number, line number, or timestamp.
      MIT

    • Alabama Code

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to retrieve the full current text of any state statute section by citation, along with its amendment history, repealed/transferred status, neighboring sections, and any pending future-effective version. It also performs live full-text keyword search across actual section body text to find statutes by topic.
      270 npm
      MIT

    • ask-your-data

      WillisK-0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to answer plain-English questions by listing and describing database tables, running read-only SQL queries, and searching a folder of policy documents.
      MIT
    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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: public act metadata, provision full text by citation, full-text search, chapter listing, citation graph traversal, change tracking, and data health. There is no overlap between lookup_public_act and get_document, and search is clearly scoped to stored provisions. An agent can reliably select the right tool for each task.

    Naming Consistency4/5

    Most names follow a predictable verb_noun pattern (lookup_public_act, get_document, get_chapter_outline, get_cross_references, list_changes). The bare verb 'search' and the noun phrase 'data_status' are minor deviations but remain readable and unambiguous in context.

    Tool Count5/5

    Seven tools are well-scoped for a legal reference server: retrieval, search, navigation, cross-referencing, change tracking, and status reporting. Each tool earns its place with no redundant capabilities. The count sits comfortably in the typical 3-15 range.

    Completeness4/5

    The surface covers core read-only legal research workflows: lookup by citation, full-text retrieval, search, chapter outlines, citation following, change history, and data currency. Minor gaps exist—no direct way to list public acts by year or fetch a public act's full text—but agents can work around these using search and citation references.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources