nl-eli-mcp
Related Servers
Alternatives to nl-eli-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn intelligent MCP server that enables AI agents to crawl, index, and semantically search official framework documentation using local RAG. It prevents hallucinations by providing precise, up-to-date documentation excerpts directly into the AI's context window.1-
- AlicenseCqualityDmaintenanceAn MCP server that integrates with the Agent.ai API to provide web text extraction, web screenshots, and YouTube transcript capabilities through a dynamic function loading system.10014 npm4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.18 npmISC
- AlicenseAqualityDmaintenanceAn MCP server that indexes reference repositories and provides tools for AI coding agents to retrieve lossless code context, enabling reasoning over codebases larger than the agent's context window.82Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding assistants access to up-to-date API documentation via RAG by crawling documentation sites, indexing them into a vector store, and enabling semantic queries.MIT
- FlicenseNot gradedqualityDmaintenanceThis MCP server provides LLMs with a live, curated knowledge base of AI agent research, world models, and source-code reviews, enabling personalized and context-aware responses. Users can either connect to the hosted knowledge or build and host their own vault.-
TDQS
Scored across 6 tools
Each tool targets a clearly distinct operation: searching acts, fetching act metadata, fetching act text, searching cases, fetching a specific decision, and describing coverage. There is no realistic overlap that could lead an agent to pick the wrong tool.
All tools share the nl_ prefix, which creates a recognizable namespace, but the internal pattern is not uniform: nl_get_* uses verb-first naming, while nl_case_search is object-first and nl_coverage is a bare noun. This is a minor inconsistency rather than a confusing mix.
Six tools is well-scoped for a legal information connector covering both legislation and case law. Each tool serves a necessary retrieval or orientation purpose, and none feels redundant.
The set covers search, metadata retrieval, and full-text retrieval for acts, plus metadata-based search and full-decision retrieval for case law. The dedicated coverage tool explicitly documents limitations and fallbacks, which closes the main practical gap in legal data connectors.