Studio Ghibli
Server Details
Studio Ghibli fan API (films, people, locations, species, vehicles)
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
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-studio-ghibli
- GitHub Stars
- 0
- Server Listing
- studio-ghibli
TDQS
Scored across 41 tools
The set contains multiple overlapping Pipeworx meta-tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions), and several Polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, bet_research) can be confused for edge discovery versus execution risk. The Studio Ghibli entity tools are clearer, but the mixed domains and layered router variants make tool selection error-prone.
Most names use snake_case, but the convention is mixed: some are plural noun collections (films, people, locations), some are singular getters (film, person, location), one is an awkward outlier (species_one), and many are verb-led actions (ask_pipeworx, validate_claim, compare_entities). The pattern is readable overall but not predictably uniform.
41 tools is heavy, especially since the server is named Studio Ghibli but only about 10 tools relate to Ghibli entities; the rest are broad Pipeworx research, monitoring, memory, and prediction-market tools. This makes the count feel inflated and poorly scoped for the apparent server identity.
For the Ghibli domain, the surface provides list-and-get coverage for films, people, locations, species, and vehicles, which covers basic read-only lookup needs but lacks search-by-title/name or richer discovery operations. The overall set is also split across two unrelated domains, so no single domain is fully covered end-to-end.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
bet_research2 fields 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": "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 (\"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."
- 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."
Related MCP Connectors
An API of Ice and Fire — A Song of Ice and Fire (books/characters/houses)
SWAPI MCP — wraps the Star Wars API (swapi.dev, free, no auth)
Star Wars API (SWAPI) as a remote MCP server: films, people, planets, species, starships, vehicles.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides access to the SWAPI Star Wars API, enabling users to query characters, planets, films, species, vehicles, and starships with automatic pagination and caching.13 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Rick and Morty characters, locations, and episodes using the Rick and Morty API with no authentication required.2 npmMIT
- FlicenseAqualityDmaintenanceEnables anime search and retrieval of details on works, series, episodes, people, organizations, staff, and broadcast schedules via the Annict REST API.14-
- AlicenseNot gradedqualityDmaintenanceMCP server for querying the Star Wars universe via the SWAPI API, providing access to characters, films, starships, vehicles, species, and planets.ISC
Glama MCP Gateway
Add one secure layer between your agents and this server.