Skip to main content
Glama
132,589 tools. Last updated 2026-05-11 00:41

"How to Find People on Twitter by Name" matching MCP tools:

  • Find people who hold or have held officer positions (director, secretary, member, partner) at companies registered in a jurisdiction, by name. Returns a list of officer candidates each with an officer_id, name, and (where the registry exposes it) the number of appointments held. Use the officer_id in get_officer_appointments to retrieve every company that person has been appointed to. This is the entry point for 'follow the human, not the company' investigations.
    Connector
  • Fetch the complete list of countries supported by GlobKurier. Each country entry contains: 'id' (numeric country ID required by other tools), 'name' (country name), 'iso_code' (ISO 3166-1 alpha-2 or regional code), EU membership status, road transport availability, and postal code formats. ALWAYS call this tool first to resolve country IDs before calling search_products, get_product_addons, or get_search_url. Find the country by name or iso_code, then use its 'id' field value.
    Connector
  • Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector
  • Send a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.
    Connector
  • Send a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.
    Connector
  • The Twitter for agents — broadcast a message to a public topic namespace that any agent monitoring that topic can read. Returns estimated reach (agents previously active on the topic) and pioneer status if you're first. Broadcasts count toward x711_hive_trending — high-volume topics rise to the top. Requires API key. Returns: { broadcast_id, topic, namespace, reach_before, reach_label, how_others_read }. Cost: $0.02.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • ship-on-friday MCP — wraps StupidAPIs (requires X-API-Key)

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • [BROWSE] List all active brands on the platform. Returns name, slug, headline, description, and product/brief counts. Use a brand slug with list_drops or list_briefs to filter by brand.
    Connector
  • Search Correkt's catalog of over 10 million products. Use this tool to find products by name, description, or category. Always use this before adding anything to cart. Tips: - Include price filters when the user mentions a budget - Use sort=price_asc to find cheapest options - Check suggestion field if results seem off — it may correct spelling - Page through results if first page doesn't have what you need
    Connector
  • [BROWSE] List all active brands on the platform. Returns name, slug, headline, description, and product/brief counts. Use a brand slug with list_drops or list_briefs to filter by brand.
    Connector
  • List the registry of platform skills — discrete how-to guides for one specific task each (e.g. 'gate-an-endpoint', 'add-a-cron-job', 'add-rag-search'). Each entry is a name, one-line purpose, and category. Use this to find the right skill, then call `read_skill(name)` to load the full pattern. When in doubt about how a Hatchable feature works, **list_skills first**. The skills are the canonical, agent-tested patterns. They beat guessing or reading the verbose docs. Filter by `query` (matches name + purpose) or `tag` (auth, data, ai, ops, etc.). Without filters, returns the full registry (~35 entries).
    Connector
  • Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector
  • Search for existing entities (people, galleries, museums, auction houses, institutions, foundations, collectors) by name. Use this before creating a new entity to check for duplicates — the system includes ~2,500 major galleries, museums, and auction houses. Returns matching entities for autocomplete-or-create flow. If no match is found, create a new entity via create_entity.
    Connector
  • Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents
    Connector
  • Find recipes using natural language search. Use this tool when: - User refers to a recipe by partial name, description, or keywords (e.g., "run my GitHub PR recipe", "the slack notification one") - User wants to find a recipe but doesn't know the exact name or ID - You need to find a recipe_id before executing it with RUBE_EXECUTE_RECIPE The tool uses semantic matching to find the most relevant recipes based on the user's query. Input: - query (required): Natural language search query (e.g., "GitHub PRs to Slack", "daily email summary") - limit (optional, default: 5): Maximum number of recipes to return (1-20) - include_details (optional, default: false): Include full details like description, toolkits, tools, and default params Output: - successful: Whether the search completed successfully - recipes: Array of matching recipes sorted by relevance score, each containing: - recipe_id: Use this with RUBE_EXECUTE_RECIPE - name: Recipe name - description: What the recipe does - relevance_score: 0-100 match score - match_reason: Why this recipe matched - toolkits: Apps used (e.g., github, slack) - recipe_url: Link to view/edit - default_params: Default input parameters - total_recipes_searched: How many recipes were searched - query_interpretation: How the search query was understood - error: Error message if search failed Example flow: User: "Run my recipe that sends GitHub PRs to Slack" 1. Call RUBE_FIND_RECIPE with query: "GitHub PRs to Slack" 2. Get matching recipe with recipe_id 3. Call RUBE_EXECUTE_RECIPE with that recipe_id
    Connector
  • Search the National Drug Code (NDC) directory by labeler company, brand name, product NDC, or application number. Returns labeler name, brand name, generic name, dosage form, route, active ingredients, DEA schedule, listing type, and packaging details. Drug products are not linked by FEI; use this tool with company name to find drugs at a company. Related: fda_search_drugs (application-level data with submissions), fda_drug_labels (full product labeling), fda_search_nsde (NSDE cross-reference).
    Connector
  • Read a single RAI request by ID. Works from either side of the relationship — the user can be the requester or the target artist. TRIGGER: "show me the request from [name]," "details on that request," "what did [requester] ask for." Find the request_id via list_rai_requests — never ask the user for it.
    Connector
  • Search for username across 15+ social/dev platforms (GitHub, Reddit, X/Twitter, LinkedIn, Instagram, TikTok, Discord, YouTube, Keybase, HackerOne, etc.). Use for OSINT investigations and identity verification. Free: 30/hr, Pro: 500/hr. Returns {username, total_found, platforms: [{name, exists, url, status_code}]}.
    Connector
  • Search for a token's CoinGecko coin ID by name, symbol, or contract address. Use this first if you're unsure of the correct coin_id for scan_token or validate_trade. Example: search 'pepe' to find the correct coin ID.
    Connector
  • Public leaderboard of fomox402 agents. WHAT IT DOES: returns the top broker-registered agents by activity, ranked according to the chosen `sort`. Read-only, no auth required, safe to call frequently (cached server-side for 30s). WHEN TO USE: scout opponents before bidding, find a name to follow, or measure your standing among autonomous agents. PARAMS: - limit (default 25, max 100): how many agents to return - sort (default 'bids'): 'bids' — most bids ever placed (activity proxy) 'recent' — most-recent bid timestamp (who's playing right now) 'won' — total $fomox402 winnings claimed (skill proxy) RETURNS: { agents: [{ name, address, bids, wins, winnings_raw, last_bid_at, created_at }], total }. RELATED: get_me (yourself), list_games (current rounds).
    Connector
  • The Twitter for agents — broadcast a message to a public topic namespace that any agent monitoring that topic can read. Returns estimated reach (agents previously active on the topic) and pioneer status if you're first. Broadcasts count toward x711_hive_trending — high-volume topics rise to the top. Requires API key. Returns: { broadcast_id, topic, namespace, reach_before, reach_label, how_others_read }. Cost: $0.02.
    Connector