Vaquill-AI/vaquill-mcp
OfficialRelated Servers
Alternatives to Vaquill-AI/vaquill-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides AI assistants access to the CourtListener legal database (US court opinions, dockets, RECAP, PACER, oral arguments, judges) and the full eCFR federal regulations via the official CourtListener API v4. It supports bring-your-own-key authentication and is designed for use with MCP-compatible clients like Claude, VS Code, and Cursor.343MIT
- AlicenseAqualityBmaintenanceMCP server for U.S. federal law that enables searching the U.S. Code, CFR, Federal Register, case law, and bills, with citation verification against primary sources to prevent hallucinations.11MIT
- AlicenseAqualityAmaintenanceMCP server for free U.S. case-law and court-docket search via CourtListener, providing tools for opinion search, docket lookup, citation verification, and more.105 npm1MIT
- FlicenseAqualityDmaintenanceMCP server for Legalize.dev, enabling AI to query and understand legal frameworks across countries via a structured legislation API.131-
- AlicenseAqualityAmaintenanceAn MCP server for accessing Turkish legislation (laws, regulations, decrees) via the Adalet Bakanligi API, providing search, full-text retrieval, and structured citations.532 PyPIApache 2.0
- AlicenseNot gradedqualityFmaintenanceAn MCP server that provides comprehensive US legislation.11 npm38MIT
TDQS
Scored across 25 tools
Nearly every tool targets a distinct resource and action, and the descriptions make the differences clear. The only real ambiguity is the deliberate generic search/fetch fallbacks alongside search_us_statutes and get_us_statute_section_text, but the descriptions explicitly direct agents to prefer the native tools.
The naming is overwhelmingly consistent: snake_case verb_noun with get, list, create, update, delete, resolve, and test. Minor deviations are the bare fallback names 'search' and 'fetch', plus slight inconsistency between 'get_section_changes' and 'get_watch_change_diff', but these do not undermine the overall pattern.
At 25 tools, the server is at the heavy end of the borderline range. There are useful batch and coverage tools, but several compatibility duplicates and fine-grained section lookup variants could likely be consolidated without losing functionality.
The tool surface is remarkably complete for its domain: citation resolution, search, metadata, full text, batch operations, hierarchy browsing, coverage discovery, cross-references, definitions, change history, and a full watch lifecycle including delivery logs and testing. There are no obvious dead ends or missing operations for the stated purpose.