Space Feeds
Server Details
Space 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-space-feeds
- GitHub Stars
- 0
- Server Listing
- space-feeds
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters have genuinely unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all answer 'find me data / what can I ask', distinguished only by long prose caveats. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, bet_research, polymarket_kalshi_spread, release_calendar_markets) similarly requires the agent to read multiple paragraphs to pick correctly. The descriptions themselves repeatedly say 'PREFER OVER X' and 'use Y instead', which is an admission that selection is hard.
Everything is snake_case, which is consistent, but the verb_noun convention is only partly followed: verb-first names (fetch_feed, read_feed, resolve_entity, validate_claim, subscribe) coexist with noun-first names (entity_profile, company_facts, prediction_calibration, recent_alerts, resolution_audit, kalshi_weather_edge). The domain prefixes (polymarket_*, updown_*, archive_*, ask_pipeworx_*) are readable but not systematic across the set.
47 tools is far too many for a server named 'Space Feeds', whose feed capability is only three tools (list_feeds, read_feed, fetch_feed). The rest is an unrelated grab bag of SEC/EDGAR, prediction markets, memory, subscriptions, AI visibility and dependency scanning — a count and scope mismatch relative to the stated purpose.
Individual sub-domains are reasonably covered in isolation: feeds have list/read/fetch, memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, and the Polymarket tooling is unusually thorough. But as a single surface it has no coherent domain to be complete against, and there are gaps such as any way to enumerate packs/catalog or manage stored memories in bulk.
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
- MIT
- -
- AlicenseAqualityBmaintenanceUnofficial MCP server for memecorp.us, a meme and hot-take feed for AI agents. Read the feed and comments with no key; with an agent API key, post, react, comment and set a persona.857 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Spaces AI Marketplace that lets AI agents browse, join, and play in shared spaces via natural language.137 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.