"General search for the term 'good'" matching MCP tools:

• ibge_noticias

  IBGE Brasil MCP

  Searches and lists already-published IBGE news articles and press releases. Use this to find recent IBGE publications or announcements about a survey or topic — when an indicator was released, or news mentioning a term like "censo". Results are sorted newest-first; with no parameters it returns the 10 most recent items. Parameters: - busca: free-text term to match (e.g. "PIB", "censo") - tipo: "release" (official publication of survey results) or "noticia" (general news); omit for both - de / ate: date range, format DD/MM/AAAA (e.g. de="01/01/2024", ate="31/12/2024") - destaque: true to return only featured items - quantidade: how many to return (default 10, max 100); pagina: page number to page through more Each item returns: title, type (release/news), publication date, editoria (section), related products/surveys, a featured flag, a plain-text summary, and a link to the full article. The header reports the total count and current page. Examples: - Latest 10 news: (no parameters) - Search census: busca="censo" - 2024 news: de="01/01/2024", ate="31/12/2024" - Releases only: tipo="release" Use a different tool when: - Scheduled/upcoming release dates (not yet published) → ibge_calendario Behavior: read-only and idempotent — a live GET against the public IBGE Notícias API. Returns a Markdown list.

  Connector

• get_faq

  mcp-server

  Search RealOpen's frequently asked questions by keyword and/or category. Use this when a user asks a specific question about RealOpen's process, security, timing, taxes, closing, proof of funds, or other product details — returns up to 20 matching entries. When no entries match, responds with the list of available categories so the caller can refine the query. Prefer this over guessing from general knowledge.

  Connector

• eurlex_get_cases

  eur-lex-mcp-server

  Search CJEU (Court of Justice of the EU) and General Court case law — judgments, orders, and Advocate General opinions. Distinct from eurlex_search_documents because case law uses CELEX sector 6 and practitioners search it differently: by case number, court, party name, or AG opinion type. Keyword search matches against English expression titles and CELEX strings — full-text body search is not available. Case numbers follow the pattern C-{num}/{year} for CJEU and T-{num}/{year} for General Court (e.g. C-131/12). Returns case identifier, court, date, human-readable document type, and title (where available). Use eurlex_get_document with the CELEX number to fetch the full judgment text.

  Connector

• list_industries

  Eveoy — Verified In-Store Foot Traffic ($24.99/customer)

  Return the list of industries Eveoy serves — 23+ B2C sectors across retail, food, beauty, hospitality, pets, and more. Use this when the user wants to: - Check whether Eveoy supports their vertical ("do you do coffee shops?") - See the full list of supported industries - Confirm an industry before pricing or booking a pilot Trigger phrases include: "what industries does eveoy support", "do you work with QSR", "list verticals", "is eveoy good for fitness studios", "what categories", "what sectors". Returns: { industries: string[], count: number, notes: string }. Each entry is a canonical sector name suitable for downstream use. Do NOT use this for: pricing (use get_pricing) or general Eveoy questions (use ask_eveoy). Cost: free. Latency: <100ms. Read-only. Cacheable. Deterministic.

  Connector

• firecrawl_search_feedback

  firecrawl-mcp

  Send structured feedback on a previous `firecrawl_search` result. **Call this immediately after a search where you used the results** so we can improve search quality and refund 1 credit (search costs 2). Pass the `searchId` returned by `firecrawl_search` (the `id` field on the response) and tell us: - **rating** — overall result quality: `good`, `partial`, or `bad`. - **valuableSources** — which result URLs were actually useful, and a short reason why. - **missingContent** — **the most important field.** An ARRAY of specific pieces of content you expected to find but didn't. One entry per missing piece, each with a short `topic` and an optional longer `description`. Examples: `{"topic":"enterprise pricing","description":"no pricing tier table for the Enterprise plan was returned"}`, `{"topic":"API rate limits"}`, `{"topic":"comparison vs competitors"}`. **Be specific** — these aggregate across teams and tell us what to index next. Do not pack multiple topics into one entry. - **querySuggestions** — how the query or response shape could be improved (e.g. "would have liked official docs first", "should boost github.com"). **Substantive-feedback requirement** (zero-effort feedback is rejected with HTTP 400): - `good` — must include at least one `valuableSources` entry - `partial` — must include `valuableSources` or at least one `missingContent` entry - `bad` — must include at least one `missingContent` entry or `querySuggestions` **Time window:** Feedback must be submitted within ~2 minutes of the search. Beyond that, the call returns HTTP 409 with `feedbackErrorCode: "FEEDBACK_WINDOW_EXPIRED"` — do not retry, just move on. Same goes for any 4xx response: do not retry-loop. **Behaviors:** - Idempotent per `searchId`. Re-submitting for the same id returns `alreadySubmitted: true` with `creditsRefunded: 0`. - Refund only applies to billable searches; preview teams are blocked. - Failed searches cannot receive feedback (the search itself already returned an error you can act on). - **Daily refund cap (per team, per UTC day, default 100 credits).** Once a team's `creditsRefundedToday` reaches `dailyRefundCap`, the response returns `dailyCapReached: true` with `creditsRefunded: 0`. The feedback is still recorded for search-quality improvement — only the credit refund is gated. **Stop calling this tool for the rest of the UTC day** when you see `dailyCapReached: true`. **When to call:** Right after processing a search result. If the result didn't help, send rating `bad` with a clear `missingContent` — that is just as valuable as a `good` rating. **Usage Example (good rating with valuable sources + missing content):** ```json { "name": "firecrawl_search_feedback", "arguments": { "searchId": "0193f6c5-1234-7890-abcd-1234567890ab", "rating": "good", "valuableSources": [ { "url": "https://docs.firecrawl.dev/features/search", "reason": "Most up-to-date description of /search." } ], "missingContent": [ { "topic": "Pricing for the search endpoint", "description": "No pricing tier table for /search specifically." }, { "topic": "Rate limits", "description": "Per-team RPS for /search not documented." } ], "querySuggestions": "Boost docs.firecrawl.dev for queries that mention 'firecrawl'" } } ``` **Usage Example (bad rating, what was missing):** ```json { "name": "firecrawl_search_feedback", "arguments": { "searchId": "0193f6c5-1234-7890-abcd-1234567890ab", "rating": "bad", "missingContent": [ { "topic": "Recent benchmarks", "description": "All results were >12 months old." }, { "topic": "Comparison vs Algolia" } ] } } ``` **Returns:** `{ success, feedbackId, creditsRefunded, creditsRefundedToday, dailyRefundCap, dailyCapReached?, alreadySubmitted?, warning? }` JSON.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• browse_collections

  Remember Me Collections

  Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code prefix (e.g. "en", "de", "ja", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.

  Connector

• search_products

  TrustRails

  HOW TO CALL THIS TOOL — read before every call: Decompose the user's request into filters first. Only what's left over goes in query. STEP 1: brand name → brand filter. STEP 2: product category → category filter. STEP 3: price → min_price/max_price. STEP 4: what remains → query. BAD: query='Sony headphones under £200' | GOOD: brand='Sony', category='Headphones', max_price=200, no query. BAD: query='tablet' | GOOD: category='Tablets', no query. BAD: query='smartwatch' | GOOD: category='Wearables', no query. BAD: query='macbook neo' | GOOD: brand='Apple', category='Laptops', query='neo'. BAD: query='Samsung QLED TV' | GOOD: brand='Samsung', category='TVs', query='qled'. If brand+category alone cover what the user wants, omit query entirely. Only put differentiating terms in query: model lines (neo, ultra, oled), variants, model numbers (WH-1000XM5, s25 ultra). CROSS-CATEGORY NOTE: Gaming headsets → category='Headphones', query='gaming headset'. The Gaming category is consoles/controllers/accessories only. Always set lite=true. If 0 results, broaden the query or drop filters. Use get_product for full specs. Search 26,000+ deduplicated UK electronics products across multiple retailers with price comparison. Covers: Laptops, Desktops, Phones, Tablets, Headphones, Monitors, TVs, Cameras, Keyboards, Mice, Speakers, Gaming, Wearables, Printers, Networking, Storage, Audio, Drones, Cables & Chargers. All prices in GBP. Returns summary data: title, brand, price, availability, category, purchase link, offer_count. MANDATORY PRICE COMPARISON: For any product relevant to the user's needs, if offer_count > 1, you MUST call get_product before responding — never mention multiple offers without presenting the full comparison. A response is incomplete if it references offer_count > 1 without retailer pricing details. Show: cheapest retailer, all other prices with the difference, exact savings amount, delivery differences if relevant. The offers[] array is sorted cheapest first. Even when the user doesn't explicitly ask about price, if offer_count > 1 it's always worth mentioning the savings. For spec-based queries (RAM, ports, screen size, weight etc.), search first then call get_product on top 3-5 results — do not assume specs from titles. STOCK: When availability is out_of_stock, mention it as an alternative and suggest checking back — do not silently omit it.

  Connector

• get_vehicle_details

  FINN Auto - Car Subscription

  Get full specifications, equipment, all images, and pricing per term for a specific vehicle. Use a vehicle_id from search_vehicles results. IMPORTANT: Always show `detail_url` as a clickable link — it points to the FINN configurator where the user picks term and km. To produce a direct checkout link for a specific term + km combination (and optionally a one-time Fahrzeugbereitstellung), call `get_subscription_pricing` and use the `checkout_url` it returns. Never construct checkout URLs yourself. The `vehicle_id` field is an internal API identifier — never display it to users.

  Connector

• search_nodes

  Diagrams MCP

  Search for diagram nodes by keyword across all providers and services. For targeted browsing when you know the provider, use list_providers -> list_services -> list_nodes instead. Args: query: Search term (case-insensitive substring match). Returns: List of matching nodes with keys: node, provider, service, import, alias_of (optional). Sorted by relevance: exact match first, then prefix, then substring.

  Connector

• get_related_terms

  Arco Lexicon

  Returns the full relationship graph for a given Lexicon term. Each related term includes: the related term's slug and title, a plain-English description of the relationship, a direction (inbound or outbound), and a canonical URL. Read-only. No LLM calls. Use this when you need to understand how terms connect — use lookup_term instead when you need a definition.

  Connector

• get_sources

  Arco Lexicon

  Returns all published Arco sources for a term — Lexicon entries, blog articles, wiki pages, and podcast episodes — ordered by recommended reading sequence. Read-only. Use this when you need a reading list or reference list for a term. Use cite_term instead when you need a formatted citation for a specific publication type.

  Connector

• hemmabo_search_availability

  HemmaBo Host Booking Engine

  Check whether a specific property is available for the requested dates. Use this tool after the user has selected a property from hemmabo_search_properties and wants to confirm availability before getting a quote. Do NOT use for general browsing — use hemmabo_search_properties instead. Returns available=true/false with conflict details and same-month alternative date windows when unavailable. Use the propertyId from search with the exact checkIn/checkOut range; omit guests to check dates only, or pass it to get host-source totals for that party size in the returned alternative windows.

  Connector

• forum_create_topic

  argo-mcp

  Create a new forum topic (bug report, feature request, or general discussion). Always call forum_search first to check for duplicates. Call forum_list_categories to get the correct categoryId.

  Connector

• people

  Comicvine

  Browse Comic Vine's comic-book creator directory (writers, artists, inkers, letterers, colorists). Filter by name; paginate with limit/offset. NOT a general biography search — for actors use TMDb, for general bios use Wikipedia.

  Connector

• openlibrary_search_books

  openlibrary-mcp-server

  Full-text book search across Open Library works. Supports field filters (title, author, subject, publisher, ISBN, language) and returns work-level records with edition counts, cover IDs, and reading availability. Use query for general search or combine specific field filters. Results are work-level — drill into editions via openlibrary_get_editions.

  Connector

• get_my_schedule

  ssuMCP

  Returns the authenticated student's u-SAINT timetable grouped by course. Without year and term it returns the current u-SAINT selected semester; pass both year and term to fetch a specific semester. Term values: 1=spring, 2=summer, 3=fall, 4=winter. Requires mcp_session_id with the SAINT provider linked via start_auth. Returns AUTH_REQUIRED with a loginUrl if SAINT is not authenticated — show the loginUrl to the user and ask them to open it in a browser, then retry this call with the returned mcp_session_id.

  Connector

• smithsonian_list_terms

  smithsonian-mcp-server

  Enumerate the valid term vocabulary for an indexed Smithsonian filter field. Call this before using smithsonian_search or smithsonian_explore filters to discover exact term strings — guessing filter values produces empty results. Returns the distinct terms sorted by object count descending, so the most-populated terms appear first.

  Connector

• string_enrichment

  STRING Database MCP Server

  This tool retrieves functional enrichment for a set of proteins using STRING. - If queried with a single protein, the tool expands the query to include the protein’s 10 most likely interactors; enrichment is performed on this set, not the original single protein. - For two or more proteins, enrichment is performed on the exact input set. - When calling related tools, use the same input parameters unless otherwise specified. - Focus summaries on the top categories and most relevant terms for the results. Always report FDR for each claim. - Report FDR as a human-readable value (e.g. 2.3e-5 or 0.023). - IMPORTANT: Remember to suggest showing an enrichment graph for a specific category of user interest (e.g., GO, KEGG) - Very large responses are capped while preserving category diversity. - Use `expand_category` to return only one category with expanded term coverage and per-term gene details. - If a row has `preferredNames_omitted: true`, do not infer which proteins are in that term from the returned rows. Use `string_functional_annotation` with the same proteins/species and `detail_for_term` set to the exact term ID. Output fields (per enriched term): - category: Term category (e.g., GO Process, KEGG pathway) - term: Enriched term (GO ID, domain, or pathway) - number_of_genes: Number of input genes with this term - number_of_genes_in_background: Number of background genes with this term - ncbiTaxonId: NCBI taxon ID - preferredNames: Canonical protein names, only when the full per-term list is short enough to show - proteinCount: Number of proteins matching this term - preferredNames_omitted: True when the gene list was omitted instead of showing a misleading partial list - p_value: Raw p-value - fdr: False Discovery Rate (B-H corrected p-value) - description: Description of the enriched term Response metadata: - input_gene_name_mapping: Only included when displayed gene lists contain submitted identifiers that differ from STRING preferred names. - category_summary: Total and returned term counts per category; use `expand_category` for categories where `truncated` is true or where the user wants deeper category-specific detail. - truncated_categories / omitted_categories: Categories with terms not shown in the current response.

  Connector