Skip to main content
Glama
650,545 tools. Updated 2026-10-14 07:11

"A search for information related to 'augment'" matching MCP tools:

  • Fast substring lookup of symbol DEFINITIONS by name: rows {name, kind, filePath, startLine, repositoryName} (displayName only when distinct from name), no ranking, no semantic. Cheaper alternative to locate (mode:symbol) for latency-sensitive pre-fetch (grep-augment hook); interactive search should prefer locate/find_node. Reads the latest indexed revision, no ref pin.
    ConnectorNo auth
  • Brave Local Search API returns enriched information (address, phone, hours, rating) for location-search results. Access requires the Brave Search API Pro plan; currently US-only. Two-step flow: first call `brave_web_search` with `result_filter=locations` to obtain `locations.results[].id`, then pass them here. NOTE: This tool takes location IDs from a prior web-search response; if you have a free-text query, call `brave_web_search` first.
    ConnectorOAuth
  • Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.
    ConnectorNo auth
  • Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.
    ConnectorNo auth
  • 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.
    ConnectorAPI key
  • 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.
    ConnectorAPI key

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Adds safety hooks to AI coding tools by providing enforced proxy tools (safe_write, safe_edit, safe_bash, safe_read, safe_delete) that validate operations through a configurable hook chain before execution, preventing destructive commands, file deletions, and secret exposure.
    MIT

Matching MCP Connectors

  • Web search for AI agents. Ranked results with page passages already extracted, plus URL to markdown.

  • Live stock information

  • 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.
    ConnectorAPI key
  • 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 the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    ConnectorNo auth
  • 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 the address behind a Nansen label (public figure, fund, exchange wallet) - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    ConnectorNo auth
  • Search domains in the deletion cycle: expired, in redemption, or pending delete. Still held by the current registrant, with time-sensitive acquisition windows. Filter by lifecycle status, TLD, age range, length, and character set. Note: registrars may renew a domain after it expires, and expiry information here is gathered through multiple channels, so some domain statuses may not match live WHOIS. Related: monitor, deleted, whois.
    ConnectorNo auth
  • Get one Celestia-related YouTube video cached on this server (metadata plus transcript), by video id. Celestia-only cache — does NOT fetch arbitrary YouTube videos or search YouTube at large (use a dedicated YouTube tool for that). Find ids via list_videos or search.
    ConnectorNo auth
  • Get average monthly search volume, competition level, and top-of-page bid ranges for a SPECIFIC list of keywords, with no expansion into related terms. Use this when the user already has keywords in mind and wants them sized: "how much traffic are these worth?". For discovering new keywords instead, use get_google_ads_keyword_ideas. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.
    ConnectorNo auth
  • Listings Grailed's own product page recommends as "similar" to one listing -- the same related-items shelf shown on grailed.com's own listing-detail page. id is the listing's numeric id, from a search, sold-listings, or collection result's own id field. An id for a listing that does not exist returns a not-found error.
    ConnectorNo auth
  • Listings Grailed's own product page recommends as "similar" to one listing -- the same related-items shelf shown on grailed.com's own listing-detail page. id is the listing's numeric id, from a search, sold-listings, or collection result's own id field. An id for a listing that does not exist returns a not-found error.
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • Return accommodation-level context, apartment list, images, detail information and weekly availability for one public accommodation. Use this after search results to inspect all apartments belonging to one accommodation and to explain location, descriptions and detail notes. For price and bookability comparison for a specific week, prefer search_apartments with weekId.
    ConnectorNo auth
  • Return public ski area information, facts, images, ski maps and related ski resorts. Use this for destination context and recommendations, not for apartment prices or availability; use search_apartments for live week-specific accommodation results.
    ConnectorNo auth
  • Read-only. Fetch the full canonical Markdown for a single spec page by its slug: YAML frontmatter (title, status, category, sources, related slugs) plus the rendered body. Use this once you have a slug from `search` or `list_topics`. If you only have keywords, call `search` first.
    ConnectorNo auth
  • Search academic papers from IACR ePrint Archive. Args: query: Search query string (e.g., 'cryptography', 'secret sharing'). max_results: Maximum number of papers to return (default: 10). fetch_details: Whether to fetch detailed information for each paper (default: True). Returns: List of paper metadata in dictionary format.
    ConnectorNo auth
  • Literature review and related-paper discovery. Given a seed paper (arXiv id, DOI, or OpenAlex id) or a topic query, returns semantically similar and recommended scholarly papers to expand a reading list or systematic review, via Semantic Scholar recommendations with an OpenAlex related-works fallback. Keyless. [$0.03/call]. Params — id: paper arXiv id, DOI, or OpenAlex id; doi: alias for id (DOI form); q: query (alternative to id — relevance search); maxItems: 1-50 Example params: {'doi': '10.48550/arXiv.1706.03762', 'maxItems': 10}
    ConnectorNo auth
  • Render the destination recommendations carousel. Always call get_recommended_destinations first for a new search, then pass its destinations (and related fields) here. For a follow-up that narrows an existing list, call only this tool with the filtered destinations. Do not invent destination cards.
    ConnectorNo auth