Fetch posts from Mastodon timelines including home, public, or local feeds to monitor social activity and content.
MIT
204,280 tools. Last updated 2026-06-14 23:34
"Mastodon" matching MCP tools:
- Fetch trending hashtags from Mastodon to discover popular topics and conversations. Specify how many tags to retrieve for content discovery.MIT
- Post text content to Mastodon with options for visibility, media attachments, scheduling, and content warnings.MIT
- Search for accounts, hashtags, or posts on Mastodon using specific queries and filters to find relevant content across the platform.MIT
- Manage Mastodon interactions: post statuses, read timelines, reply, boost, favorite, search, view profiles, follow users, and check notifications.MIT
- Post single or threaded statuses to any Mastodon instance. Requires instance URL and access token with write:statuses scope. Optionally override per-instance character limit. Returns posted post ID and URL.MIT
Matching MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides tools for interacting with Mastodon, enabling users to create toots with customizable visibility and attach media files with descriptions.Last updated48MIT
- Alicense-qualityBmaintenanceComprehensive MCP server for Mastodon integration, enabling AI assistants to read timelines, post statuses, manage accounts, search, and more on any Mastodon instance.Last updated1MIT
- Retrieve currently trending hashtags from any Mastodon-compatible Fediverse instance. Specify the domain to fetch trending tags.MIT
- Retrieve currently trending posts from a Mastodon-compatible fediverse instance by providing its domain, with an optional limit on the number of posts.MIT
- Compose platform-specific social media posts with share copy and clickable intent URLs to quickly spread startup signal results and the MCP install command.MIT
- Retrieve the full comment thread for a government contracting opportunity, including ancestor structure and raw comment data. Requires a completed matchawards signup to access member discussions.MIT
- Sync every configured communication connector and retrieve sync counts per source. This includes Discord, Telegram, Matrix, Slack, email, and Mastodon.MIT
- Sync recent Mastodon posts from a public or hashtag timeline into memory. Supports optional instance, hashtag, and access token parameters.MIT
- Access trending Mastodon content from the Fediverse. Returns post text, author, and engagement metrics like reblogs, favorites, and replies without authentication.MIT
- Get trending hashtags from Mastodon with usage counts. Track popular topics on the decentralized social network.MIT
- Retrieve trending topics from social media platforms like Twitter, Mastodon, and LinkedIn to identify popular conversations and content opportunities.MIT
- Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).Connector
- "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.Connector
- Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.Connector
- Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).Connector
- Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.Connector