juba-mcp
Related Servers
Alternatives to juba-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA specialized MCP server for Argentine legal professionals, enabling legal research, document processing, case analysis, and practice management through integration with official Argentine legal databases.8MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables searching and retrieving judicial decisions from the Uruguayan National Public Jurisprudence Database (BJN).-
- FlicenseAqualityBmaintenanceMCP server that provides access to Argentine legal documents (legislation, CSJN jurisprudence, international treaties) with verifiable provenance including SHA256 hashes and source URLs, enabling legal professionals to search and verify citations.13-
- FlicenseNot gradedqualityAmaintenanceUnified MCP server for Argentine legal sources, enabling access to 11 databases including jurisprudence, legislation, official bulletins, and court records through a single connector for Claude Desktop.63-
- AlicenseAqualityCmaintenanceMCP server for searching and extracting official announcements, decrees, and resolutions from the Argentine Official Gazette (Boletín Oficial de la República Argentina). It enables LLMs to perform real-time searches and retrieve verbatim legal text with complete juridical fidelity.1419 npm3MIT
- FlicenseNot gradedqualityDmaintenanceRemote MCP server that provides access to over 285K Argentine court rulings and user's own case files via Streamable HTTP transport.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: juba_advanced_search offers field-specific filtering, juba_get_fallo retrieves full ruling text by ID, and juba_search provides basic keyword search for summaries. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent 'juba_' prefix with descriptive snake_case suffixes (advanced_search, get_fallo, search). This predictable pattern enhances readability and coherence across the tool set.
With 3 tools, the server is well-scoped for its domain of accessing court rulings. Each tool earns its place by covering distinct aspects: basic search, advanced search, and full-text retrieval, avoiding bloat or thin coverage.
The tool surface provides complete coverage for the domain of court ruling access: search (basic and advanced) and retrieval of full texts. There are no obvious gaps, as agents can find rulings and access their details without dead ends.