Skip to main content
Glama

Packagephobia

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Packagephobia MCP — install-size analysis for npm packages

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
33.3% over 46 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-packagephobia
GitHub Stars
0
Server Listing
mcp-packagephobia

TDQS

A3.9/5.0

Scored across 32 tools

Disambiguation3/5

The four ask_pipeworx* variants (ask_pipeworx, _beta, _grounded) plus deep_research all route questions to the same 5,961-tool backend, and _beta is explicitly identical to the stable router today, creating real selection ambiguity. The six polymarket_* tools and bet_research overlap in prediction-market analysis, though the very detailed descriptions (PREFER OVER, START HERE, grounded vs casual) do help an agent pick. ai_visibility_check vs scan_competitor_ai_presence and validate_claim vs ask_pipeworx_grounded also share pipelines.

Naming Consistency4/5

Most names follow a predictable snake_case verb_noun pattern (compare_entities, resolve_entity, discover_tools, validate_claim, polymarket_fill_risk). A few are bare verbs/nouns (remember, recall, forget, subscribe, size) and some carry a source prefix (polymarket_*, pipeworx_*) while others don't, but nothing is chaotic or camelCase-mixed.

Tool Count2/5

32 tools is well above the ~15 ceiling for a coherent set and lands in the 'too many' band. It is somewhat defensible for a broad data-gateway, but the surface spans unrelated domains (AI visibility, prediction markets, npm sizing, memory, subscriptions, onboarding), so individual tools struggle to earn their place and the count is high for any single stated purpose.

Completeness4/5

For a broad data-routing gateway the surface is fairly complete: discovery/onboarding, question answering, entity resolution, comparison, research, memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts) and feedback are all covered. Gaps are minor — no raw 'fetch a specific filing/record by id' retrieval tool and thin package-ecosystem coverage beyond npm.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources