Skip to main content
Glama

Social Signal

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Social Signal — post-VOLUME TIME SERIES across the open social networks that

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
20.9% over 62 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-social-signal
GitHub Stars
1
Server Listing
social-signal

TDQS

A4/5.0

Scored across 38 tools

Disambiguation3/5

Descriptions are exhaustive, but the set contains several near-duplicate query entry points: ask_pipeworx, ask_pipeworx_beta (explicitly 'identical universal router'), ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, and validate_claim all compete for the same 'answer a question' intent. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread, polymarket_edge_tracker, bet_research, kalshi_weather_edge) also overlaps heavily. Memory and subscription tools are clearly distinct, saving the score from being lower.

Naming Consistency4/5

All names are consistently snake_case and readable, with only minor verb-first vs noun-first drift (resolve_entity/validate_claim vs company_facts/entity_profile) and a pipeworx_ prefix cluster. No camelCase/snake_case mixing. The variation is stylistic rather than chaotic.

Tool Count2/5

38 tools is well above the practical 'heavy' range and feels overloaded for a single server, particularly given the redundant ask_pipeworx variants and the dense prediction-market cluster. A number of these could be consolidated into one router with mode flags rather than separate tools.

Completeness4/5

Surface is broad: query/routing, entity resolution, company facts, prediction-market edges/arbitrage/fill-risk, social volume/activity, memory, subscriptions, AI visibility, and developer utility checks. Minor gaps remain (no direct low-level fetch tools for most data packs; X/Twitter explicitly excluded), but agents can work around them via the routers.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 29 tool updates
    • Changedai_visibility_check1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "entity": "Tesla"
+  }
+]
    • Changedask_pipeworx3 fields changed
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Changedask_pipeworx_beta4 fields changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Changedask_pipeworx_grounded4 fields changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "question": "What was Apple's fiscal 2023 revenue?"
+  }
+]
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
    • Addedcompany_facts
    • Changedcompare_entities1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "type": "company",
+    "values": [
+      "AAPL",
+      "MSFT"
+    ]
+  }
+]
    • Changeddeep_research9 fields changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "depth": "quick",
+    "question": "What is the current US unemployment rate and how has it changed over the past year?"
+  }
+]
      • addedInput schema / properties / ask
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / input
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / message
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / prompt
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / q
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • addedInput schema / properties / query
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
      • changedInput schema / properties / question / description
        Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."
      • addedInput schema / properties / text
        Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • Changedentity_profile1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]
    • Changedforget4 fields changed
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
    • Changedgenerate_llms_txt1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "url": "https://pipeworx.io"
+  }
+]
    • Addedkalshi_weather_edge
    • Changedpipeworx_feedback1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
+    "type": "other"
+  }
+]
    • Changedpipeworx_trending1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "window": "7d"
+  }
+]
    • Changedpolymarket_arbitrage1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "topic": "Fed rate decision"
+  }
+]
    • Changedpolymarket_edge_tracker1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "days": 14,
+    "window": "1wk"
+  }
+]
    • Changedpolymarket_edges3 fields changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "limit": 5,
+    "window": "1wk"
+  }
+]
      • changedInput schema / properties / min_edge_pp / description
        Previous value: -"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee."
      • changedInput schema / properties / slippage_pp / description
        Previous value: -"Assumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model."New value: +"Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw |edge| before ranking and Kelly sizing, ON TOP OF Polymarket's own taker fee — which is NOT zero (rate 0.04-0.07 depending on category, read off each market's own published fee schedule; see fees_pp_applied on every row and fees.ts for the full schedule). Bump slippage for very thin partitions; drop to 0 if you have a smarter fill model — the fee still applies regardless."
    • Changedpolymarket_fill_risk1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
+    "side": "buy_yes",
+    "size_usd": 1000
+  }
+]
    • Changedrecall4 fields changed
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
    • Changedrecent_changes1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "since": "30d",
+    "type": "company",
+    "value": "AAPL"
+  }
+]
    • Addedrelease_calendar_markets
    • Changedremember10 fields changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "key": "target_ticker",
+    "value": "AAPL"
+  }
+]
      • addedInput schema / properties / content
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / data
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / k
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • changedInput schema / properties / key / description
        Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."
      • addedInput schema / properties / label
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}
      • addedInput schema / properties / text
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • addedInput schema / properties / v
        Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}
      • changedInput schema / properties / value / description
        Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."
    • Addedresolution_audit
    • Addedresolution_diff
    • Changedresolve_entity1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]
    • Changedscan_competitor_ai_presence1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "entities": [
+      "Pipeworx",
+      "Zapier"
+    ]
+  }
+]
    • Changedscan_dependency1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "package": "left-pad"
+  }
+]
    • Changedsearch_within1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "query": "supply-chain risk",
+    "text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter."
+  }
+]
    • Changedsuggest_questions1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "topic": "finance"
+  }
+]
    • Changedvalidate_claim1 field changed
      • addedInput schema / examples
        Added value: +[
+  {
+    "claim": "Apple's fiscal 2023 revenue was $383 billion"
+  }
+]
  3. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]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 (\"when-will-bitcoin-hit-150k\"), 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."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."
  4. 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • 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 (\"when-will-bitcoin-hit-150k\"), 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."
  5. 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