Skip to main content
Glama
pawelojdowski

SAOS MCP

by pawelojdowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SAOS MCP

No user-submitted related servers found.

    Related Servers

    • legal_mcp

      barwojcik
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic search over Polish court judgments and legislative acts via MCP. Allows LLMs to retrieve legal documents using natural language queries.
      Apache 2.0

    • Law Scrapper MCP

      numikel
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-powered legal research and analysis of Polish legal acts from the Sejm API. Provides comprehensive search, document retrieval, metadata analysis, and content access for legal documents from Dziennik Ustaw and Monitor Polski.
      13
      21
      MIT

    • prawo-pl-mcp

      matematicsolutions
      A
      license
      A
      quality
      B
      maintenance
      Unified MCP server for Polish legal data, enabling search and retrieval across case law, legislation, company register, tax rulings, public procurement, and EU sources through four aggregated tools.
      4
      1
      Apache 2.0

    • Slovak Law MCP Server

      Ansvar-Systems
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables querying and analyzing Slovak legislation via natural language, including full-text search, provision retrieval, and EU law integration.
      60 npm
      2
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: searching judgments, fetching a specific judgment by ID, and listing courts. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent pattern: saos_ + verb + noun (search_judgments, get_judgment, list_courts). This makes the API predictable and easy to navigate.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its purpose of accessing court judgments. This is an appropriate size for a focused legal database, avoiding unnecessary complexity.

    Completeness5/5

    The tool set covers the complete workflow: find courts for filtering, search for judgments with rich query options, and retrieve full details for a specific judgment. There are no obvious gaps for typical use cases.

    Maintenance

    ActivityStale
    ResponsivenessSyncing

    Resources