Skip to main content
Glama

Server Details

NYT MCP — wraps The New York Times Developer APIs (developer.nytimes.com)

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
40.4% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-nyt
GitHub Stars
1
Server Listing
mcp-nyt

TDQS

A3.8/5.0

Scored across 35 tools

Disambiguation3/5

Most tools have distinct, well-documented purposes, but the ask_pipeworx family is problematic: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, and ai_visibility_check overlaps with scan_competitor_ai_presence. The six polymarket tools are individually described but form a dense cluster where agents may still hesitate between edges, arbitrage, bet_research, and fill_risk.

Naming Consistency3/5

All names are snake_case and readable, but conventions are mixed: some are imperative verb_noun (validate_claim, resolve_entity), some are noun phrases (top_stories, recent_alerts, books_bestsellers), and others use product prefixes (polymarket_*, ask_pipeworx_*). This is not chaotic, but it is not a single predictable pattern either.

Tool Count2/5

At 35 tools, this is a heavy surface for an MCP server and exceeds the usual practical range. The breadth is partly justified by a universal data-gateway purpose, but duplicate/variant tools such as ask_pipeworx_beta and the large polymarket cluster inflate the count without proportionally unique value.

Completeness4/5

The set covers a broad gateway lifecycle: discovery, query routing, entity resolution, comparison, memory, subscriptions, alerts, and feedback. Minor gaps remain (e.g., no explicit update-memory tool and no general article-body or web-fetch tool), but agents can work around them through existing query and routing tools.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous 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 (\"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."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous 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."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.