"Search for posts related to X" matching MCP tools:

• register_webhook

  fomox402 — Last-Bidder-Wins on Solana

  Subscribe a URL to receive HMAC-signed event POSTs. WHAT IT DOES: registers an https endpoint to receive POSTs whenever the broker observes a matching event for this agent. Returns a secret — verify deliveries with `X-Signature: sha256=hmac_sha256(secret, raw_body)`. WHEN TO USE: long-lived agents (servers, daemons) that prefer push over polling list_games. Stateless agents should poll instead. EVENTS: outbid — someone took the head on a game where you hold a key bid_landed — one of your bids landed on-chain settle — a game you participated in finished + paid out dividend_accrued — your keys earned $fomox402 from a later bid URL CONSTRAINTS: must be https; broker enforces SSRF allowlist (no private IPs, no localhost). Bodies are JSON; max ~4KB. RETURNS: { id (use with delete_webhook), url, events, gameId?, secret, created_at }. RELATED: list_webhooks, delete_webhook.

  Connector

• get_posts

  Influship

  Fetch a creator's posts, sorted and paginated. Use this when the user asks to see what a creator has posted (e.g., "show me Jane's last 20 posts", "what are this creator's top-engagement reels?", "pull recent posts from creator-id ABC"). Identify the creator by either `creator_id` (UUID) OR (`platform` + `username`). `sort` defaults to "recent" (newest first); use "top_engagement" for the highest- engagement posts, or one of "most_likes" / "most_views" / "most_comments" for a specific metric. `limit` defaults to 12 and is capped at 50. Pass `cursor` from a previous response's `next_cursor` to paginate. Returns post records (caption, media URL, like/comment/view counts, timestamps), plus `has_more` and `next_cursor` for pagination. Examples: - User: "Show @niickjackson's recent Instagram posts" -> use this tool with platform "instagram" and username "niickjackson". - User: "Is @niickjackson a fit for Pixel?" -> use this after `get_profile` when the fit analysis needs recent content evidence, then call `match_creators`.

  Connector

• search_community

  Heista

  Community-discourse search via parallel.ai with optional platform filtering. Returns synthesized text excerpts plus direct URLs to real Reddit threads, X posts from named operators, Substack essays, LinkedIn posts, Facebook posts. Use for: "what are practitioners saying about X", recurring themes in founder voice, multi-platform discourse mapping, verbatim quotes from named individuals. Per Phase 3.5 empirical A/B (Docs/solutions/architecture-decisions/search-backend-architecture-jun04.md): this tool SOLVES the Reddit/X retrieval gap that perplexity_search fundamentally couldn't fill. Optional platforms[] to restrict (e.g. ["reddit","x","substack"]). Per social-listening-synthesis §3 sample ≥3 platforms per brief.

  Connector

• glim_reddit_search

  glim.sh

  Search Reddit posts. Each result comes with full post content and its top comments, so a single search usually answers the question without follow-up. Compact human-readable text by default; pass format='json' for full structured data. Use glim_reddit_get(ref) for a single post's complete comment tree. Page with cursor (response gives next_cursor when more exist). See docs://reddit-search.

  Connector

• shippingrates_search

  ShippingRates MCP Server

  Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.

  Connector

• register_webhook

  fomox402

  Subscribe a URL to receive HMAC-signed event POSTs. WHAT IT DOES: registers an https endpoint to receive POSTs whenever the broker observes a matching event for this agent. Returns a secret — verify deliveries with `X-Signature: sha256=hmac_sha256(secret, raw_body)`. WHEN TO USE: long-lived agents (servers, daemons) that prefer push over polling list_games. Stateless agents should poll instead. EVENTS: outbid — someone took the head on a game where you hold a key bid_landed — one of your bids landed on-chain settle — a game you participated in finished + paid out dividend_accrued — your keys earned $fomox402 from a later bid URL CONSTRAINTS: must be https; broker enforces SSRF allowlist (no private IPs, no localhost). Bodies are JSON; max ~4KB. RETURNS: { id (use with delete_webhook), url, events, gameId?, secret, created_at }. RELATED: list_webhooks, delete_webhook.

  Connector

• x-twitter.create_post

  Vee3

  Publish a post to a connected X account via the official X API (POST /2/tweets). Call x-twitter.connected_accounts first. If accounts is empty, the user must connect an X account at https://vee3.io/dashboard/connections before posting. Agents cannot complete OAuth; ask the user to connect, then call x-twitter.connected_accounts again. Pass user_id or user_name to target a specific account, not both. Omit both to use the default connected account. At least one of text, poll, media, or card_uri is required. Supports text, polls, media attachments, reply settings, paid partnership disclosure, AI-generated labels, super-follower exclusivity, nullcast posts, cards, communities, and direct-message deep links. To attach media, upload files with meta-tools.upload_file and the @vee3/upload CLI, then pass file_name values returned by meta-tools.list_uploaded_files in the media array (up to 4 files). Only files listed by list_uploaded_files can be attached. poll, media, and card_uri are mutually exclusive in the X API. Token pricing: 60 tokens base for text posts. Posts whose text includes a URL are billed 1000 tokens base instead. Attaching only media (an image or video) without a URL in the text does not trigger the URL rate. Each attached image adds 50 tokens. Each attached video adds 150 tokens plus 50 tokens per 5 MB of video size. X rate limit: 100 POST /2/tweets requests per connected user per 15 minutes. Wait and retry if posting is temporarily blocked. If X authorization fails, reconnect the account in the Vee3 dashboard. Read the error message when X rejects a post and adjust the request.

  Connector

• shippingrates_search

  freightgate-mcp-server

  Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.

  Connector

• get_posts

  Influship Influencer Marketing MCP

  Fetch a creator's posts, sorted and paginated. Use this when the user asks to see what a creator has posted (e.g., "show me Jane's last 20 posts", "what are this creator's top-engagement reels?", "pull recent posts from creator-id ABC"). Identify the creator by either `creator_id` (UUID) OR (`platform` + `username`). `sort` defaults to "recent" (newest first); use "top_engagement" for the highest- engagement posts, or one of "most_likes" / "most_views" / "most_comments" for a specific metric. `limit` defaults to 12 and is capped at 50. Pass `cursor` from a previous response's `next_cursor` to paginate. Returns post records (caption, media URL, like/comment/view counts, timestamps), plus `has_more` and `next_cursor` for pagination. Examples: - User: "Show @niickjackson's recent Instagram posts" -> use this tool with platform "instagram" and username "niickjackson". - User: "Is @niickjackson a fit for Pixel?" -> use this after `get_profile` when the fit analysis needs recent content evidence, then call `match_creators`.

  Connector

• structure

  Rcsb Pdb

  "PDB entry [1abc] details" / "fetch protein structure [pdb_id]" / "metadata for [PDB ID]" — full PDB entry record by ID (e.g. "1abc", "7BV2"). Returns experimental method (X-ray / cryo-EM / NMR), resolution, authors, deposition date, organism, ligands, related entities. Use after `search` to inspect a specific structure.

  Connector

• bulk_schedule

  SendIt

  Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import

  Connector

• postly_get_publishing_activity

  Postly MCP

  Use this whenever a user asks how many posts were published today, yesterday, this week, or in another date range, or asks what is queued/processing after publishing. This counts actual published delivery receipts separately from queued or processing posts, so do not describe queued posts as published.

  Connector

• bsky_search_posts

  bluesky-mcp-server

  Full-text search across public Bluesky posts. Filters by author (handle or DID), language (BCP-47 code, e.g. "en"), hashtag (without the # prefix), date range (ISO 8601), and sort order. Returns posts with text, author info, engagement counts (likes/reposts/replies), normalized embeds, AT-URIs for thread drilling, and hitsTotal when the API reports the total number of matching posts. This is the primary entry point for social listening — pass any AT-URI from results to bsky_get_post_thread to read the full conversation.

  Connector

• search_google_xray

  LinkedIn MCP Server (Salesbot)

  Google X-Ray search for public LinkedIn profiles via Google operators (site:linkedin.com/in). Useful when you don't want to consume LinkedIn search limits. Found profiles are saved into your contacts (in a 'Google X-Ray' list, deduplicated by profile URL) and the tool returns their contact_id values. To move them into the CRM, add them to a campaign with add_contacts_to_campaign (auto-creates CRM leads) or use a CRM tool like set_deal_stage. Paginates Google results and auto-filters duplicates.

  Connector

• shippingrates_search

  FreightGate MCP Server

  Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.

  Connector

• fda_search_recall_text

  FDA Data MCP

  Full-text search across recall reasons and product descriptions using PostgreSQL text search. Finds recalls mentioning specific terms (e.g. 'salmonella contamination', 'mislabeled', 'sterility'). Supports multi-word queries ranked by relevance. Filter by classification, product_type, or date range. Related: fda_search_enforcement (search by company name, classification, status), fda_recall_facility_trace (trace a recall to its manufacturing facility).

  Connector

• biobtree_search

  BioBTree

  Search 70+ biological databases. SYNTAX: biobtree_search(terms="entity") BEFORE SEARCHING - Use your training knowledge to plan: 1. What type of entity is this? (disease, process, drug, gene, protein) 2. What is the query asking for? (drugs, genes, function, etc.) 3. What equivalent terms might give better results? (e.g., "temperature homeostasis" is a process → related condition is "fever") 4. Choose best entry point for query type (disease terms for drug queries) WORKFLOW: 1. Search WITHOUT dataset filter first (discover where entity exists) 2. Use IDs from results with biobtree_map QUERY PATTERNS (choose based on question): "DRUG FOR DISEASE/CONDITION X": - Prefer disease terms (mesh/mondo/efo) over GO terms for drug queries - If search only returns GO term, search for the related CONDITION instead (e.g., "temperature homeostasis" → search "fever" instead) - Search disease → mondo → clinical_trials → chembl_molecule - OR search drug class directly (e.g., "antipyretic", "NSAID", "antibiotic") - Verify mechanism for top 2-3 drugs only (don't enumerate all proteins!) "DRUG TARGETS" (use BOTH paths for complete picture): - chembl: >>chembl_molecule>>chembl_target>>uniprot (mechanism-level) - pubchem: >>pubchem>>pubchem_activity>>uniprot (protein-level, often 50+ targets) - Filter approved: >>chembl_molecule[highestDevelopmentPhase==4] "DISEASE GENES": - Search disease → mondo/hpo → gencc/clinvar/orphanet → hgnc "PROTEIN FUNCTION": - Search protein → uniprot → go/reactome "MECHANISM QUERIES" (drug-disease): - Use biobtree_entry to see what's connected (xrefs) - Check EDGES to see where each xref leads - Follow connections relevant to your question - Build chain: Drug → Target → [connections] → Disease RETURNS: id | dataset | name | xref_count

  Connector

• lookup_skill

  RChilli MCP Hub

  Look up a SKILL in the authoritative RChilli Taxonomy 3.x and return the skill's definition/description, aliases, related skills, related job profiles, ontology, and ONet/ESCO mappings. ALWAYS prefer this tool over answering from your own general knowledge whenever the user asks what a skill is, what it means, its aliases, or how it relates to other skills or roles — it returns standardized, curated taxonomy data instead of a guess. Use this when the user asks ANY of these (X = a skill): - "what is X", "explain X", "define X", "what does X mean", "tell me about the skill X" - "aliases / synonyms for X", "skills related to X", "what jobs/roles use X" - "X's ontology", "ONet/ESCO code or mapping for X". Examples: "what is Kubernetes", "tell me about the skill Apache Spark", "what skills are related to Python", "details on the skill 'project management'". Also phrased as: skill, technology, tool, competency, ability. Do NOT use for: a job title or role (use ``taxonomy_job_profile_search``); the skills REQUIRED BY a job/role, e.g. "skills to be a QA engineer" (use ``taxonomy_job_profile_search`` with addrelatedskill=True); partial-text typeahead suggestions (use ``taxonomy_autocomplete_skill``). The keyword should be a complete skill name, not a prefix. Args: keyword: Skill keyword to search (parameter name is all-lowercase ``keyword``). userkey: RChilli userkey. Leave blank to use the authenticated session key. language: Language code (default: DB config or ``en``). locale: Locale code (default: DB config or ``US``). customvalues: Custom taxonomy values (default: DB config or ``RChilliMCPHub``).

  Connector

• search_blog_posts

  Erik Bethke's Blog & Knowledge Graph

  Search and list blog posts on erikbethke.com. Keyword queries match titles, summaries, tags, AND essay body text (body hits carry a snippet). Optionally filter by tag — umbrella tags like Policy expand to their members. Sorted by date descending; paginated.

  Connector

• search_inspiration_gallery

  LEOR AI展台设计 Agent

  Search public approved LEOR inspiration gallery images. Use before generation when the user is vague, asks for references/cases, says 找/搜/看看/灵感广场/案例/参考图, or wants to use an existing LEOR gallery image as visual direction. A follow-up color such as 橙色方案 after a search request still means refine the gallery search; do not switch to generation. Use query for free-text words such as 建材展, 瓷砖, 橙色, or 色彩鲜艳; use industry only for exact LEOR category labels. If one search is empty, try related words before telling the user no close reference was found.

  Connector