Nypl
Server Details
NYPL Digital Collections MCP.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 46.0% over 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-nypl
- GitHub Stars
- 1
- Server Listing
- mcp-nypl
TDQS
Scored across 33 tools
The descriptions do a lot of work to separate tools, but there is real functional overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions, and ask_pipeworx_beta openly states it 'currently matches ask_pipeworx exactly.' Similarly entity_profile / recent_changes / compare_entities / resolve_entity form a cluster an agent could easily confuse, and six polymarket_* tools plus bet_research crowd one domain.
Nearly everything is lowercase snake_case (ask_pipeworx, entity_profile, polymarket_arbitrage, resolve_entity, validate_claim), which is predictable and readable. Minor deviations are bare nouns/verbs (search, item, recall, forget, subscribe) rather than verb_noun, but no camelCase or mixed-case chaos appears.
At 33 tools this is heavy, but the server spans genuinely large domains (universal data routing, entity research, prediction markets, subscriptions, memory, plus NYPL search). Each tool earns some place, though the ask_* trio and the polymarket_* family push it toward bloat.
As a Pipeworx gateway the surface is broad (routing, grounding, entity resolution, subscriptions, memory, feedback). But for the server's apparent NYPL identity, coverage is thin: only search and item exist, with no collection browse, filtering, or metadata-only operations, a notable gap for a library-domain server.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research1 field changed- changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
1 tool update
- Changed
bet_research1 field changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +]
Related MCP Connectors
Victoria and Albert Museum (V&A) Collections MCP.
Minneapolis Institute of Art (Mia) collection MCP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenancePapers With Code MCP — browse ML research papers and their code repositories.32 npmMIT
- AlicenseNot gradedqualityCmaintenanceInteract with the Cooper Hewitt API with MCP.2MIT
- AlicenseAqualityBmaintenanceMCP server for searching and retrieving full-text pages from the Library of Congress, including newspapers, books, and manuscripts, via the loc.gov API.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server for the National Parliamentary Library of Georgia's Iverieli repository, enabling search, metadata retrieval, PDF downloads, and rendering of historical newspaper pages as JPEGs and tiles.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.