Skip to main content
Glama

Fyyd

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

fyyd MCP — open podcast directory

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

TDQS

B3.2/5.0

Scored across 38 tools

Disambiguation2/5

There are multiple near-duplicate entry points: ask_pipeworx, ask_pipeworx_beta (admitted to be identical right now), ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all answer 'get me data/a question' with fuzzy boundaries. The Polymarket cluster overlaps badly too — bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_edge_tracker all surface the same opportunities, and scan_competitor_ai_presence is just a wrapper over ai_visibility_check.

Naming Consistency4/5

Names are overwhelmingly consistent snake_case with a verb_noun or clear noun_phrase shape (search_episodes, resolve_entity, validate_claim, compare_entities). Minor deviations exist — a few bare nouns (categories, latest_episodes, top_podcasts) and version-suffixed twins (ask_pipeworx_beta) — but nothing mixed-convention or unreadable.

Tool Count2/5

38 tools is well past the heavy threshold and is a severe mismatch for a server branded as the fyyd podcast directory, which only needs ~7 of them. The remaining ~31 tools are unrelated Pipeworx platform, Polymarket, memory, and subscription surfaces bolted onto the same set.

Completeness3/5

The podcast core is mostly covered (search_podcasts, search_episodes, get_podcast, get_podcast_by_url, latest_episodes, top_podcasts, categories) and memory/subscription lifecycles are complete, but there is no fetch-episode-by-id tool even though search_episodes returns fyyd episode ids — a real dead end. The overall surface also sprawls across domains unrelated to the stated purpose, so coverage is uneven rather than complete.

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": "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."
  2. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."

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