Skip to main content
Glama
510,021 tools. Updated 2026-09-03 16:33

"Information about 'fetch' or related resources" matching MCP tools:

  • Read ONE entity with its sub-resources nested in a single call. Convenience over well_get_schema + well_query_records: resolves the field paths for you and returns the single record with its related data expanded. depth (relation-nesting BOUNDARY, 1-3, default 1): 1 = the entity + its direct sub-resources (emails, phones, locations, …) 2 = + the sub-resources' related scalars 3 = the full level-3 graph (LARGER payload — use when you need the whole picture) Stops at depth 3. Aggregates are excluded. Each child collection is capped at 50 rows; for a full list or to page a large child collection, use well_query_records on that child root instead.
    Connector
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    Connector
  • 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
  • Fetch bounded public security.txt text without following contacts. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    Connector
  • 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.
    Connector
  • 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)
    Connector

Matching MCP Servers

  • F
    license
    A
    quality
    C
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.
    33
    1
    MIT

Matching MCP Connectors

  • Fetch web pages and extract exactly the content you need. Select elements with CSS and retrieve co…

  • MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

  • 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.
    Connector
  • Fetch the full machine-readable rendition of a tutorial by slug: title, TL;DR, numbered steps (with text, imageUrl, tips, and YouTube videoTimestampSeconds for deep-linking), tools/materials, tags, related tutorial slugs, creator credit, recipe (with nutrition + cuisine when applicable), license, and canonicalUrl. Use this after search_tutorials to fetch step details.
    Connector
  • 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
  • Full metadata for one dataset (CKAN package_show) including its resources/distributions with download URLs. Use a dataset `name` (slug) or id from search_datasets. There is no datastore, so fetch `resources[].download_url`/`url` for the underlying data.
    Connector
  • Full dataset record by id or slug (CKAN package_show), including its resources. Each resource carries a "url" you can fetch directly to download the data (CSV/JSON/etc.) — this portal has no datastore, so there is no row-level query API.
    Connector
  • 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.
    Connector
  • Return measured end-to-end fetch timing. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    Connector
  • Report HTTPS certificate validation performed by the safe fetch transport. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    Connector
  • Fetch the selected bot record including agent_type, versions, LLM config, and related counts via GET /v1/bot/get-data.
    Connector
  • Fetch a single profile (booking page) by id. YCBM API: GET /v1/profiles/{profileId}. Use `fields` to select fields, including nested sub-resources (appointmentTypes, teamMembers, locations). Returns the profile object.
    Connector
  • Discovery helper: returns the standard prompt template, argument template, output-interpretation guide and related resources for one or all SmartMoney77 tools, so you can call them correctly without guessing. Example: { "tool": "fire_number" }.
    Connector
  • Tight 3-5 sentence summary of a URL or a raw text block, via an LLM. Give it EXACTLY ONE of `url` (a page to fetch and summarize) or `text` (raw text to summarize directly). For agents/pipelines that need a fast, information-dense digest without running their own LLM call or web fetch.
    Connector
  • TOOL for retrieving current user's owned resources and work items across the Cortex workspace. FLEXIBLE REQUEST STRUCTURE: The request accepts an object with optional fields for each resource type: - myEntitiesRequest: Fetch entities (services, resources, domains) owned by the user - myTeamsRequest: Fetch teams the user belongs to - myScorecardsRequest: Fetch scorecards associated with user's entities - myOpenPRsRequest: Fetch user's open pull requests across all Git repositories - myRequestedReviewsRequest: Fetch PRs where user is requested as a reviewer - myWorkItemsRequest: Fetch work items (Jira, Linear, Azure DevOps) assigned to the user Set one or more fields to fetch multiple resource types in a single call. All results are combined into a single response array with mixed item types. RESPONSE STRUCTURE: Returns a single array of items where each item has an 'itemType' field indicating its type: - 'entity': Catalog entities (services, resources, domains) - 'team': Teams the user belongs to - 'scorecard': Scorecards for user's entities - 'pull_request': Open pull requests authored by the user - 'review_request': Pull requests where user is requested as reviewer - 'work_item': Work items (issues/tickets) assigned to the user EXAMPLES: 1. Fetch only services: {"myEntitiesRequest": {"entityTypes": ["service"]}} 2. Fetch teams and their entities: {"myTeamsRequest": {"includeMembers": true}, "myEntitiesRequest": {}} 3. Get all work (PRs, reviews, Jira tickets): {"myOpenPRsRequest": {}, "myRequestedReviewsRequest": {}, "myWorkItemsRequest": {}} 4. Search entities with filters: {"myEntitiesRequest": {"query": "payment", "ownershipSource": "DIRECT", "entityTypes": ["service", "resource"]}}
    Connector
  • Fetch a single bill with full detail: versions, sponsorships, related/companion bills, actions, and votes. Pass the OpenStates ID (e.g., "ocd-bill/abc...") or a state/session/identifier triple.
    Connector