Skip to main content
Glama

Server Details

Comic Vine 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
42.1% over 40 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-comicvine
GitHub Stars
0
Server Listing
mcp-comicvine

TDQS

A3.6/5.0

Scored across 41 tools

Disambiguation3/5

The remarkably detailed descriptions help, but there are genuine overlaps: ask_pipeworx / ask_pipeworx_beta (explicitly 'currently matches ask_pipeworx exactly') / ask_pipeworx_grounded form a three-way cluster, and polymarket_arbitrage / polymarket_edges / polymarket_edge_tracker / polymarket_fill_risk overlap heavily on 'find and size bets'. The Comic Vine tools (character/characters, issue/issues, volume/volumes) are cleanly paired and distinguishable, but the meta-router family requires reading long prose to pick correctly.

Naming Consistency3/5

Everything is snake_case, which is a real consistency win, but two conventions are mixed: imperative verb_noun meta-tools (ask_pipeworx, resolve_entity, compare_entities, discover_tools) versus bare-noun Comic Vine tools (character, issue, search, publishers). Singular/plural pairs (character/characters, issue/issues, person/people) are readable but 'people' breaks the regular pattern.

Tool Count2/5

41 tools is heavy (25+ band), and far more importantly the count is dominated by ~31 Pipeworx gateway/meta/polymarket tools that have nothing to do with the declared Comicvine scope. A comic-book reference server carrying subscription management, LLM-visibility audits, npm dependency scans, and Polymarket arbitrage is a severe scope mismatch.

Completeness3/5

The Comic Vine surface covers browse+detail for character, issue, volume, person, and publisher, plus a general search, but the search tool advertises resources (story_arc, team, concept, location, object) that have no dedicated browse/detail tools — notable gaps for a comic reference domain. The Pipeworx half is broad, though it is largely unrelated to the server's stated purpose.

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": "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"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous 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."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
  2. 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": "when-will-bitcoin-hit-150k"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
        +  }
        +]
      • 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 (\"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."
    • Changedpolymarket_kalshi_spread1 field changed
      • 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.