Stacks
Related Servers
Alternatives to Stacks
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables AI agents to access US public library data from the federal IMLS Public Libraries Survey, including proximity searches, library system profiles, and statewide statistics.6MIT- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with a live web search tool that returns extracted, answer-ready text from web pages. Enables real-time information retrieval without any local installation or maintenance.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search a university library's catalog by keyword, title, author, subject, or ISBN, and to check each copy's real-time availability, floor location, and expected return date. Also provides recommended reading lists, new arrivals, and search-term suggestions, with raw holdings data parsed into readable output.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search the web, read and extract content from webpages, fetch JSON from REST APIs, and collect links while bypassing anti-bot protections.35 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to call typed tools compiled from ordinary websites, performing reads and verified writes through their web UIs and returning data, screenshots, and execution traces.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to search a curated catalog of practical AI books and retrieve book records, topics, reading paths, free chapters, glossary definitions, and verified claim citations. It also supports checking claims and generating citations from the catalog’s published free material.MIT
TDQS
Scored across 14 tools
Most tools have clearly distinct targets: list_branches vs get_branch, list_events, find_library, ask_library, and the watch trio (watch/list/cancel) are unambiguous. The main soft spot is the cluster around a single title — search_catalog, get_title, check_availability and estimate_wait all return title-level data and partially overlap (e.g. get_title and estimate_wait both list other formats), though the descriptions do a good job of drawing the lines and pointing to each other.
Almost everything follows a clean snake_case verb_noun pattern (get_branch, list_branches, list_events, find_library, search_catalog, check_availability, get_title, watch_title, cancel_watch, get_job_result). The only real deviations are health_check (noun_noun) and the slightly softer ask_library/estimate_wait, which are still readable and consistent with the rest.
14 tools is well within a healthy range and each one maps to a distinct capability: library lookup, branches, events, catalogue search, title detail, availability, wait estimation, a slow-agent fallback pair (ask_library/get_job_result), watch lifecycle, and diagnostics. Nothing feels padded or missing at the count level.
Discovery, branches, events, availability, alerts and a self-diagnostic path are all covered, and ask_library backstops policy questions. However the surface is read-only where the domain implies action: you can estimate a hold wait but there is no way to place or cancel a hold, and there are no account tools (my loans, holds, renewals), which are core library workflows. Also no get_event detail for individual events.