Skip to main content
Glama

Server Details

Design Feeds MCP.

The last two health checks of this connector failed. 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
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-design-feeds
GitHub Stars
0
Server Listing
Design Feeds MCP
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 47 tools

Disambiguation3/5

Several clusters have genuinely unclear boundaries: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all claim to be the routing entry point, and thirteen prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, bet_research, release_calendar_markets, etc.) overlap heavily on 'find a mispricing'. Descriptions do work hard to differentiate (beta is explicitly 'identical to ask_pipeworx right now', scan_competitor_ai_presence is ai_visibility_check fanned out), but the caller must read enormous prose to disambiguate, and the server name 'Design Feeds' actively misdescribes 44 of 47 tools.

Naming Consistency4/5

All names are lowercase snake_case with a consistent style, and most follow verb_noun (list_feeds, read_feed, fetch_feed, resolve_entity, validate_claim, compare_entities, search_within, archive_compare). Deviations are stylistic rather than chaotic: bare verbs (remember, recall, forget), noun-phrase names (polymarket_edges, kalshi_weather_edge, prediction_calibration, release_calendar_markets), and vendor-prefixed meta-tools (pipeworx_feedback, ask_pipeworx_beta).

Tool Count2/5

47 tools is heavy for any single server, and the surface spans at least six unrelated domains (RSS feeds, SEC/XBRL company research, prediction-market arbitrage, AI-visibility auditing, npm dependency scanning, agent memory). Even accepting a broad data-gateway scope, the count is inflated by near-duplicates (ask_pipeworx + beta + grounded + deep_research; four separate subscription-management tools).

Completeness4/5

Coverage of the underlying data-gateway domain is unusually thorough: entity resolution, per-period financial facts, cross-venue market pricing, settlement-clause auditing, memory, and subscription lifecycle all exist with explicit not-found/error states. Gaps are minor but real — the design-feed purpose itself has only list/read/fetch with no feed search or feed-based subscription type, and the generic fetch_url referenced inside research_row is not exposed as its own tool.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.