Skip to main content
Glama

Server Details

Developer 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-dev-feeds
GitHub Stars
0
Server Listing
mcp-dev-feeds
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters of tools are hard to tell apart: ask_pipeworx, ask_pipeworx_beta (explicitly "currently matches ask_pipeworx exactly"), ask_pipeworx_grounded, deep_research and discover_tools all route to the same catalog, and polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, polymarket_fill_risk and polymarket_edge_tracker all scan/price prediction markets. entity_profile vs company_facts vs recent_changes vs compare_entities are distinguishable only after reading long descriptions. An agent can usually pick something reasonable, but many choices are near-ties.

Naming Consistency4/5

Nearly everything is snake_case with an identifiable domain prefix (polymarket_*, updown_*, archive_*, ask_pipeworx*). Word order varies (verb_noun like list_feeds/read_feed vs noun_first like entity_profile/company_facts/archive_compare), and the beta/grounded suffixes on ask_pipeworx break the pattern slightly, but nothing is chaotic.

Tool Count2/5

47 tools is far beyond what the server's stated identity ("Dev Feeds") implies — the feed tools themselves are only three of them, with the rest being an entire financial/prediction-market data gateway plus memory and subscription plumbing. The surface is heavy and sprawling enough that selecting the right tool is itself work.

Completeness3/5

Considered as a Pipeworx data gateway the coverage is broad (entity resolution, filings, prediction markets, archives, memory, subscriptions all have lifecycle tools). But for the advertised dev-feed purpose the surface is thin: list/read/fetch a feed exists, yet there is no way to add, remove, or register a new feed source. The mismatch between name and content leaves obvious gaps for the stated domain.

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.