mcp-databnf
Related Servers
Alternatives to mcp-databnf
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for the French open-data catalogue data.gouv.fr, enabling dataset search and retrieval, organization lookup, and reuse discovery via natural language queries.80 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server to query French Open Data from data.gouv.frMIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling search and retrieval of public SensCritique data, including works, user profiles, and collections.9 npm2MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that searches library catalogs worldwide using the SRU protocol, enabling bibliographic search without API keys.1-
- FlicenseNot gradedqualityDmaintenanceMCP server for querying French railway services (SNCF) via the Navitia API, enabling station search, journey planning, and departure board retrieval.-
- AlicenseBqualityDmaintenanceMCP server that enables searching books by author via Open Library API and searching keywords inside local text files.2164 npmMIT
TDQS
Scored across 7 tools
Each tool has a distinct resource+action target, and the descriptions go out of their way to state boundaries (e.g. search_works reads titles only, list_works walks from a person to works they created; find_digitised vs list_editions is explicitly separated). The remaining overlap is on works: search_works, get_work, list_works and list_editions all touch the same resource, so an agent must read carefully, though the descriptions do resolve it.
The set follows a clean verb_noun pattern (search_authors, get_author, search_works, get_work, list_editions, list_works) with consistently snake_case naming. The only deviation is find_digitised, which names no object noun and uses a fourth verb (find), a minor inconsistency in an otherwise predictable scheme.
Seven tools is well within the ideal range and each one earns its place: a search/get pair for each of the two entity types, plus editions, creator-works and digitised-link listings. No tool looks like filler or a redundant variant of another.
The author and work lifecycles are covered end to end (search to get to editions to digitised links), with explicit notes on what each link does not reach. Gaps remain: expressions are counted by get_work but there is no tool to list them, no edition-level lookup (e.g. by ISBN), and no subject/Dewey browse, though these are workable omissions for a catalogue-browsing server.