Skip to main content
Glama

Bundlephobia

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Bundlephobia MCP — npm bundle-size analysis

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

TDQS

A3.8/5.0

Scored across 39 tools

Disambiguation2/5

Several tools occupy the same conceptual space: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and deep_research/ask_pipeworx_grounded/validate_claim all handle natural-language queries over the same sources. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) also has overlapping opportunity-detection roles that require reading long disclaimers to separate.

Naming Consistency3/5

Most Pipeworx tools follow a readable snake_case verb_noun pattern (ask_pipeworx, resolve_entity, compare_entities, validate_claim, list_subscriptions), and the polymarket_* family is consistent. However, the bundlephobia subset uses bare nouns (size, similar, history, recent_searches), and mixing product-branded names with generic utility names is not a single predictable scheme.

Tool Count2/5

39 tools is far beyond the 3-15 sweet spot, and most are unrelated to the server's stated Bundlephobia identity—only size, similar, history, recent_searches, and scan_dependency actually belong to it. The remaining Pipeworx, prediction-market, memory, and subscription tools feel bolted on, making the count heavy for the apparent purpose.

Completeness4/5

Within the bundlephobia core, the surface is reasonably complete: size analysis, alternatives (similar), historical size (history), popular packages (recent_searches), and a composite dependency check (scan_dependency) cover the main user workflows. The broader Pipeworx/prediction-market surface also has well-paired meta-tools (remember/recall/forget, subscribe/list/unsubscribe/recent_alerts, resolution_audit/resolution_diff), with only minor gaps such as an explicit package-to-package comparison tool.

Tool Schema Changelog

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

  1. 4 tool updates
    • Addedkalshi_weather_edge
    • Addedrelease_calendar_markets
    • Addedresolution_audit
    • Addedresolution_diff
  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": "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
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