MHW MCP — Monster Hunter World data (mhw-db.com, free, no auth)
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.
Scored across 40 tools
Multiple tools have overlapping or unclear boundaries. ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route questions to data sources with significant overlap. ai_visibility_check and scan_competitor_ai_presence overlap (scan is just a wrapper). bet_research, polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread all target prediction-market edge but from confusingly different angles. The Monster Hunter tools (get_armor, get_monsters, get_skills, get_weapons) are clear, but the Pipeworx meta-tool family creates real selection ambiguity.
Naming is inconsistent across the set. There's a clear verb_noun pattern in some (get_weapons, get_monsters, list_subscriptions, resolve_entity, validate_claim), but Pipeworx tools mix product names (ask_pipeworx, pipeworx_feedback, pipeworx_trending), generic verbs (recall, remember, forget, subscribe, unsubscribe), and domain-specific compound names (polymarket_kalshi_spread, kalshi_weather_edge, release_calendar_markets). No consistent prefix or verb convention unifies the set.
40 tools is far too many for a coherent server surface. The server appears to be a grab bag: a handful of Monster Hunter World lookups, a large Pipeworx data-router family, prediction-market tools, memory utilities, and feedback/subscription plumbing. Many tools are near-duplicates or single-use wrappers (ask_pipeworx_beta duplicates ask_pipeworx; scan_competitor_ai_presence wraps ai_visibility_check). This count exceeds the high end of the appropriate range for any single coherent purpose.
The Monster Hunter subset is complete for basic lookups (armor, monsters, skills, weapons) but has no obvious update/create/delete needs. The Pipeworx data-access surface is thorough — query, grounded query, research, discovery, suggestions, entity resolution, comparison, verification — but the prediction-market workflow has gaps: polymarket_edges and polymarket_arbitrage produce signals but there is no actual order-placement tool (fill_risk is analysis-only). Memory tools (remember/recall/forget) are complete. Overall the domain is so diffuse that completeness is hard to assess, and the betting workflow ends at analysis without execution.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
company_factskalshi_weather_edgerelease_calendar_marketsresolution_auditresolution_diffbet_research2 fields changedInput 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"
+ }
+]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."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]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."VALORANT reference data MCP (valorant-api.com).
Digimon API MCP (digi-api.com).
D&D 5e MCP — wraps the D&D 5th Edition API (free, no auth)
Add one secure layer between your agents and this server.