mcp-toolbox
Related Servers
Alternatives to mcp-toolbox
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables querying and analyzing Spanish (BOE) and EU (EUR-Lex) legal documents, with advanced search, PDF extraction, and cross-reference detection.851 npm2MIT
- AlicenseAqualityBmaintenanceEnables Claude, Cursor, and other MCP clients to search Spanish BOE/BORME gazettes, open and forthcoming EU funding calls, and TED public procurement notices through read-only tools that return live JSON with source links.31MIT
- AlicenseBqualityCmaintenanceEnables LLMs like Claude to query the official Spanish BOE API for consolidated legislation, daily summaries, and auxiliary government tables.3161MIT
- AlicenseAqualityBmaintenanceEnables AI clients to search and retrieve official bulletins, articles, and PDFs from the Melilla official gazette (BOME), including fast local index queries.19MIT
- AlicenseAqualityDmaintenanceEnables querying Spanish BOE consolidated legislation, daily summaries, and legal reference data through natural language using the Model Context Protocol.56MIT
- AlicenseAqualityBmaintenanceEnables AI assistants and agents to query Spanish public statistics from INE, official BOE publications, and Catastro property data via typed, read-only tools with structured, source-citable results.8MIT
TDQS
Scored across 3 tools
search_boe and get_boe_document form a clean search/retrieve pair over the same corpus, and triage_tenders targets a clearly different dataset (TED/PLACSP) with a different output shape. The only mild overlap is that both search_boe and triage_tenders are 'query a corpus with keywords and filters' operations, so an agent could occasionally hesitate about which entry point to use.
All names are snake_case with a leading verb (search_/get_/triage_), which reads predictably. The minor deviation is that search_boe names the corpus rather than the object (compare get_boe_document), so the noun convention isn't fully uniform.
Three tools is thin for something branded as a 'toolbox', and the surface splits across two fairly different domains (BOE documents vs. tender triage), making the small set feel like two mini-servers glued together. It is defensible for a narrow offline read-only scope, but it sits at the borderline.
The BOE side has adequate read-only coverage (search plus fetch by identifier) for its offline scope. The tender side is a dead end: triage_tenders lists screened tenders but there is no tool to fetch a specific tender's full record or evidence detail, forcing agents to work from the list output alone.