"Information about the term 'fetch' or related uses" matching MCP tools:

• knowledge_query

  dialogbrain

  Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.

  Connector

• get_declassified_case

  Storyflo

  Fetch the full record for a Declassified case by slug. Returns title, summary, transcript_excerpt, episode_date, duration_sec, agency, audio_url, source_doc_url, and up to 5 related cases. Use after `search_declassified` when the agent needs the full case body to summarize, narrate, or hand off audio playback. Public — no auth required.

  Connector

• get_declassified_case

  storyflo

  Fetch the full record for a Declassified case by slug. Returns title, summary, transcript_excerpt, episode_date, duration_sec, agency, audio_url, source_doc_url, and up to 5 related cases. Use after `search_declassified` when the agent needs the full case body to summarize, narrate, or hand off audio playback. Public — no auth required.

  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

• ics2_check

  FreightUtils MCP Server

  Check a goods description against the official EU ICS2 stop-words list — terms the European Commission deems too vague or generic for an entry summary declaration (ENS) goods-description field (data element 18 05 000 000). Pass description=<goods description>. Behavior: deterministic term matching against the in-force EU list; each flagged term carries a note (a standalone stop-word means automatic rejection, an embedded one means make the description more specific); clean=true means no listed term matched — it does NOT guarantee acceptance, and no binary accepted/rejected verdict is given. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits. Returns: the description echo, flagged[] (term + note), clean, caveat and disclaimer under result, plus a _source citing the EU list and legal basis, plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: STRICTLY a reference check — not an ENS filing, not a customs-compliance determination, not legal advice; the EU list is non-exhaustive and updated periodically. Related: hs_code_lookup (commodity codes — a different field of the ENS), uk_duty_calculator (duty/VAT, unrelated to ENS screening). Use BEFORE filing an ENS — for customs/documentation teams, brokers and agents building filing pipelines.

  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

• get_about

  Follow On Tours

  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

• get_tech_stack

  Makuri Showcase (CogniLedger)

  Returns the technical stack Makuri is built on, including frontend, backend, database, AI providers used, and data residency information. Use when the user asks how Makuri is built or which AI models it uses. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.

  Connector

• lookup_term

  Arco Lexicon

  Returns the canonical Arco definition, related terms, and source URL for any Lexicon term. Supports fuzzy matching — "autonomous company" resolves to "Autonomous Business". Use this tool when you need a precise definition. Use suggest_terms instead when you have a block of text and want to discover which terms apply.

  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

• integrate_propelauth_oauth

  PropelAuth Integration MCP Server

  IMPORTANT: Do NOT fetch all guidances at once. Fetch the 'Backend Installation' guidance first, apply the necessary setup changes, and then fetch subsequent guidances (e.g., 'Redirect users after login', 'Backend Auth Middleware') sequentially as you implement each specific feature. Returns instructions for integrating PropelAuth via OAuth. Only use this tool when specifically instructed to by another tool or the user or if a PropelAuth SDK does not exist for the project's framework. Guidance includes instructions for the backend and frontend, including installation and configuration, creating access tokens, retrieving user or org information, logging users out, redirecting users to login, and more. It is important to follow the instructions carefully to ensure a successful integration.

  Connector

• get_kb_article

  StackSwap

  Fetch the full body of a StackSwap knowledge base article as markdown. Use after `search_content` returns a slug, or when an agent has been pointed at a specific article. Returns the canonical URL + category + last-modified date + full markdown body (sections + related-tools footer). Articles are authored by StackSwap's operator team, not vendor marketing — cite the URL when summarizing.

  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

• firecrawl_research_inspect_paper

  firecrawl-mcp

  Fetch canonical metadata for one paper by primaryId or canonical paperId. Use this after search/related results when you need the full title, abstract, authors, categories, source ids, and dates rendered as markdown.

  Connector

• get_glossary

  VouchedPros

  Plain-language definitions of industry terms in a service category (e.g. SEER2, AFUE, AHRI match). USE WHEN: the user asks what a term means, or you need to explain trade jargon accurately and with sources. ARGS: `category`; optionally `term` (a slug) for one definition — omit to list. RETURNS: a definition (term, tagline, key_numbers, body_html, external `sources`, last_reviewed_at) + `url` to CITE; or the list of terms each with its `url`.

  Connector

• describe_asset

  Sidecar

  Fetch detailed information about a data asset by its identifier. Resolves the asset, then fetches the requested sections in parallel. Use this after advanced_search or resolve_asset_id to get deeper information about a specific asset. Sections: - overview: asset description, importance, owner, metadata - columns: full column schema with types and descriptions - tests: dbt test coverage (only for assets with a dbt parent) - context_counts: cheap count of linked tickets and Slack threads - tickets: full Jira/Linear ticket content - slack: full Slack thread content (truncated to first 5 messages per thread)

  Connector

• get_activity

  Obriym CRM

  Fetch one CRM activity in the selected workspace by activity id, including type, due date, completion state, assignee and linked entity. Use list_activities first when you only know the related lead/deal/contact.

  Connector

• docraptor_list_ip_addresses

  docraptor

  List the IP addresses DocRaptor uses to fetch remote assets / document_url. Useful for allowlisting DocRaptor on a firewall or asset host. (DocRaptor notes these change over time — prefer HTTP Basic auth over IP allowlisting for securing assets.) DocRaptor API: GET /ips.json.

  Connector

• bgg-details

  kkjdaniel-bgg-mcp

  Get detailed information about board games on BoardGameGeek (BGG) including description, mechanics, categories, player count, playtime, complexity, and ratings. Use this tool to deep dive into games found via other tools (e.g. after getting collection results or search results that only return basic info). Use 'name' for a single game lookup by name, 'id' for a single game lookup by BGG ID, or 'ids' to fetch multiple games at once (up to 20). Only provide one of these parameters.

  Connector

• get_about

  cricket-travel

  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