Bluesky
Server Details
Bluesky MCP — wraps the AT Protocol API
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
- 28.7% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-bluesky
- GitHub Stars
- 0
- Server Listing
- mcp-bluesky
TDQS
Scored across 39 tools
Several tool clusters have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta (explicitly identical currently), ask_pipeworx_grounded, and deep_research all answering questions, or discover_tools and suggest_questions both for discovery. The detailed descriptions help differentiate most cases, but the presence of near-duplicates and multiple Polymarket/entity tools creates real ambiguity.
Tools consistently use snake_case, with the majority following a verb_noun pattern (get_feed, compare_entities, resolve_entity). There are deviations—some noun-first names (entity_profile, polymarket_arbitrage) and standalone verbs (forget, subscribe)—but the convention is readable and mostly predictable.
39 tools is well above the 25-tool threshold for a heavy set, and several are variants or overlapping (ask_pipeworx_beta duplicates ask_pipeworx). The server spans many domains, but the count feels bloated rather than well-scoped.
Coverage is broad: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, Bluesky read operations are comprehensive, and Pipeworx data tools cover querying, comparison, verification, and research. Minor gaps exist (e.g., no write operations for Bluesky, no trade execution for Polymarket), but the core lifecycle for each domain is present.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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."
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious 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." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious 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
Read public AT Protocol profiles, records, threads, backlinks and lexicons. No API key required.
Mastodon MCP — public Mastodon data via mastodon.social (no auth required)
Podcast Index MCP — wraps the Podcast Index API (podcastindex.org)
Confluence MCP — wraps the Confluence Cloud REST API v2 (OAuth)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Bluesky/AT Protocol enabling LLM clients and agents to authenticate, search, post, like, follow, and manage chat on Bluesky.8 npm1MIT
- AlicenseAqualityAmaintenanceMCP server for managing a Bluesky account, enabling posting, replying, liking, reposting, following, searching, and reading timelines/notifications via natural language.18MIT
- FlicenseAqualityBmaintenanceAn MCP server for interacting with the AT Protocol (ATProto) ecosystem, including Bluesky, providing tools for identity, profiles, and social discovery.61-
- AlicenseCqualityBmaintenanceEnables interacting with Bluesky/AT Protocol through MCP tools for posting, replying, media, timelines, and a human-approved outbox system.4MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.