Skip to main content
Glama
134,003 tools. Last updated 2026-05-13 17:48

"A server for finding information about logistics and supply chain management" matching MCP tools:

  • Search FDA import refusals (Compliance Dashboard data, not available in openFDA API). Import refusals indicate products detained at the US border. Filter by company name, FEI number, country code (e.g., CN, IN for major API source countries), or date range. Critical for evaluating international manufacturing sites and supply chain risk. Related: fda_get_facility (facility details by FEI), fda_inspections (inspection history by FEI).
    Connector
  • Get active trade policy actions currently impacting supply chain risk — tariffs, sanctions, export controls, import restrictions, and regulatory changes. Unlike news alerts that expire after 72 hours, policy adjustments persist as long as the policy is in effect and continue to modify GDI risk scores. Each policy includes the affected GDI pillar, score modifier, effective date, and source event. Used by procurement teams navigating tariff exposure, compliance officers tracking sanctions, and supply chain strategists adapting sourcing to policy shifts.
    Connector
  • Assess the best DeFi opportunity for a given capital amount and strategy. This is the "cold start" tool — call it first to understand where your capital is viable before making any moves. One call gives you chain viability, ranked opportunities, gas impact, and an actionable recommendation. Args: api_key: Your PreFlyte API key (required). asset: Token symbol, e.g. "USDC", "WETH". action: "supply" or "borrow". position_size_usd: Capital amount in USD. strategy: One of "yield_farming", "active_trading", "idle_capital". chain: "ethereum", "arbitrum", or "any" (default: "any"). trades_per_day: For active_trading strategy only. Default 10. Returns: JSON with chain viability, ranked opportunities, gas analysis, break-even calculations, and an actionable recommendation.
    Connector
  • Logic-trace driver-chain explorer — answers "WHY is this activity critical?" and "WHAT does it drive?". Traces driving predecessors backward from a target activity to project start (the "why critical" chain) and/or driving successors forward to project finish (the "what it drives" chain). Detects constraint-driven artificial criticality and cites AACE RP 24R-03 §4 when found. Supports multiple parallel critical paths (MCPM) and near-critical paths. Use this tool when investigating a single activity's logic chain. For a project-wide CP / logic health audit, use ``critical_path_validator``. Args: xer_path: server-side path to the schedule XER. xer_content: full text of the schedule XER (alternative for hosted/remote use). Supply EXACTLY ONE of path/content. target_activity_codes: list of task_codes to trace; if empty, all CP / near-critical endpoints are traced. direction: 'backward' (predecessors), 'forward' (successors), or 'both' (default). include_near_critical: also trace near-critical endpoints (within float band). output_dir: optional dir for HTML / CSV / JSON outputs. Returns: { "paths": [{chain dicts ...}], "output_files": {dashboard, csv, json}, "project_finish": "YYYY-MM-DD", "project_name": ..., "data_date": ... }
    Connector
  • Get comprehensive US energy market status for supply chain cost analysis. Returns crude oil prices (WTI and Brent), natural gas spot prices (Henry Hub), retail fuel prices (gasoline, diesel), natural gas storage versus capacity, refinery utilization rates, petroleum stock levels with week-over-week changes, and import/export flows. This is the disaggregated view behind the GDI Energy pillar — instead of a single risk number, you get the full picture of energy costs affecting manufacturing, freight, and logistics. Used by supply chain cost analysts, transportation managers, and energy procurement teams.
    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 Nansen labels of an address (EOA) or resolve a domain (.eth, .sol) Args: query: The search term - token symbol, name, or address. DO NOT include chain name here! result_type: Type filter - "token", "entity", "eoa", or "any" max_results: Maximum number of results (default: 25, max: 25) chain: Optional chain filter to narrow down token results to specific blockchain. If not further specified, leave it as None. If a chain is specified, ALWAYS use this parameter instead of adding chain name to the query string. Valid values: "ethereum", "solana", "base", "bnb", "polygon", "arbitrum", "avalanche", "optimism", etc. How to choose result_type: - token: Use when searching for a token by name, symbol, or contract address. **CRITICAL**: Use the `chain` parameter to filter by blockchain, NOT the query string! ✅ CORRECT: query="AAVE", chain="base" ❌ WRONG: query="AAVE base", chain=None - entity: Use when you want entity info by name/label (exchanges, funds, etc.) - eoa: Use when you have an address and need its labels or you have an ENS/SNS domain and need the resolved address - any: Mixed results (tokens/entities). Also auto-resolves ENS/SNS domains and, if token/entity results are empty and the query looks like an address, falls back to EOA labels. Important: - This is the only tool that can resolve domains. If you start from a domain, pass the Resolved Address to other tools. - **DOMAINS**: Strings ending in `.eth` (ENS) or `.sol` (SNS) are DOMAIN NAMES, not tokens. Use result_type="eoa" or "any" to resolve them. Examples: "vitalik.eth", "abracadabra.sol", "y22.eth" are domains that resolve to addresses. - **DO NOT** ASSUME that token is a NFT, always verify the name by using this tool first. - **DO NOT** add keyword `token` or chain names to the query string, unless this is explicitly in the token name or symbol! - **Focus** on **popular chains** like ethereum, solana, base and bnb when no chain is specified and the same token is deployed on multiple chains. - **If a chain is specified**, use the `chain` parameter to filter tokens by blockchain instead of including chain in query. - **DO NOT** rely on this endpoint for LATEST prices as this is delayed. Use `token_ohlcv` for latest prices.
    Connector

Matching MCP Servers

  • F
    license
    -
    quality
    F
    maintenance
    Provides structured access to semiconductor industry platforms to search for IP core suppliers, ASIC design services, and manufacturing resources. It enables users to estimate procurement costs, compare vendors, and query industry glossaries using natural language.
    Last updated

Matching MCP Connectors

  • Real-time supply chain risk intelligence — 24 tools, proprietary indices, predictive signals

  • Enterprise supply chain AI, warehouse optimization, logistics intelligence, real-time crypto/forex/stock data, shipping rates. 61+ MCP tools. Credit-based pricing at $0.001/credit with x402 USDC payments on Base/Polygon.

  • 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) Args: query: The search term - token symbol, name, or address. DO NOT include chain name here! result_type: Type filter - "token", "entity", "eoa", or "any" max_results: Maximum number of results (default: 25, max: 25) chain: Optional chain filter to narrow down token results to specific blockchain. If not further specified, leave it as None. If a chain is specified, ALWAYS use this parameter instead of adding chain name to the query string. Valid values: "ethereum", "solana", "base", "bnb", "polygon", "arbitrum", "avalanche", "optimism", etc. How to choose result_type: - token: Use when searching for a token by name, symbol, or contract address. **CRITICAL**: Use the `chain` parameter to filter by blockchain, NOT the query string! ✅ CORRECT: query="AAVE", chain="base" ❌ WRONG: query="AAVE base", chain=None - entity: Use when you want entity info by name/label (exchanges, funds, etc.) - eoa: Use when you have an address and need its labels or you have an ENS/SNS domain and need the resolved address - any: Mixed results (tokens/entities). Also auto-resolves ENS/SNS domains and, if token/entity results are empty and the query looks like an address, falls back to EOA labels. Important: - This is the only tool that can resolve domains. If you start from a domain, pass the Resolved Address to other tools. - **DOMAINS**: Strings ending in `.eth` (ENS) or `.sol` (SNS) are DOMAIN NAMES, not tokens. Use result_type="eoa" or "any" to resolve them. Examples: "vitalik.eth", "abracadabra.sol", "y22.eth" are domains that resolve to addresses. - **DO NOT** ASSUME that token is a NFT, always verify the name by using this tool first. - **DO NOT** add keyword `token` or chain names to the query string, unless this is explicitly in the token name or symbol! - **Focus** on **popular chains** like ethereum, solana, base and bnb when no chain is specified and the same token is deployed on multiple chains. - **If a chain is specified**, use the `chain` parameter to filter tokens by blockchain instead of including chain in query. - **DO NOT** rely on this endpoint for LATEST prices as this is delayed. Use `token_ohlcv` for latest prices.
    Connector
  • Batch-score multiple npm, PyPI, Cargo, or Go packages for supply chain risk. Takes a list of package names and returns a risk table sorted by commitment score (lowest = highest risk first). Risk flags: - CRITICAL: single publisher + >10M weekly downloads (publish-access concentration risk) - HIGH: new package (<1yr) + high downloads (unproven, rapid adoption = supply chain risk) - WARN: low publisher count + high downloads Perfect for auditing a full package.json, requirements.txt, Cargo.toml, or go.mod — paste your dependency list and get a prioritized risk report. For Go: pass full module paths (e.g., "github.com/gin-gonic/gin", "golang.org/x/net") and set ecosystem="golang". The "maintainers" column shows GitHub contributor count since Go has no centralized publisher concept. Examples: score all deps in a project, compare two similar packages, identify abandonware before it becomes a CVE.
    Connector
  • Get token information — spot on-chain details or Hyperliquid perpetual futures stats. On-chain tokens mode (default): Returns token details (name, symbol, market cap, FDV, supply, deployment date, socials) and spot trading metrics (volume, buys/sells, buyers/sellers, holders, liquidity). Perps mode: Returns Hyperliquid perp stats — mark price, funding, open interest, buy/sell pressure, trader participation. Returns: Token information as markdown. On-chain tokens fields: - **Market Cap / FDV**: Market capitalization and fully diluted valuation - **Circulating / Total Supply**: Token supply metrics - **Deployed**: When the token was deployed - **Volume (Total / Buy / Sell)**: Trading volume in USD - **Buys / Sells**: Number of buy/sell transactions - **Unique Buyers / Sellers**: Distinct trading addresses - **Total Holders**: Number of token holders - **Liquidity**: Available liquidity in USD Perps fields: - **Mark Price**: Current perp mark price - **Price Change**: Change vs previous price - **Funding Rate (hourly/annualized)**: Current funding rate - **Open Interest**: Total current open interest in USD - **Volume (Total / Buy / Sell)**: Perp volume in USD - **Net Flow (Buy - Sell)**: Buy/sell pressure in USD - **Traders**: Number of traders Example: On-chain tokens (default mode): ``` { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "timeframe": "1d" } ``` Hyperliquid perps: ``` { "mode": "perps", "tokenAddress": "BTC", "timeframe": "7d" } ``` Notes: - On-chain tokens mode uses contract addresses - Perps mode uses token symbols (e.g. BTC, ETH, HYPE) - Both modes use the same `timeframe` parameter
    Connector
  • Get trend analysis of the Global Disruption Index over time. Returns the current GDI score plus 7-day, 14-day, and 30-day comparisons with direction, velocity of change, and pillar-level momentum. Identifies which pillar is driving changes and whether risk is accelerating or decelerating. Answers: 'Is supply chain risk getting better or worse, how fast, and why?' Used by supply chain executives for weekly status briefings and by traders to time entry/exit decisions around supply chain volatility.
    Connector
  • Get ERC-20 token metadata for a token address on Mezo. Returns name, symbol, decimals, and total supply (raw and formatted). Degrades gracefully — any individual call failure returns null for that field.
    Connector
  • Get a behavioral commitment profile for any Rust crate on crates.io. Returns real signals: crate age, download volume (estimated weekly from 90-day totals), version count, publish cadence, owner count (users with publish access), team owners, and linked GitHub activity. Supply chain risks apply to Cargo too — crate owners with publish access are the attack surface. A single owner on a high-download crate is the same risk pattern as npm. Useful for: vetting Rust dependencies before adding to Cargo.toml, identifying abandonware, supply chain risk assessment. Examples: "serde", "tokio", "reqwest", "clap", "rand"
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Get ERC-20 token metadata for a token address on Ethereum mainnet. Returns name, symbol, decimals, and total supply (raw and formatted). Degrades gracefully — any individual call failure returns null for that field.
    Connector
  • Walk the full receipt chain for a DID and return a signed integrity statement. Public, no auth. Returns chain length, chain root (deterministic over the chain hash), latest entry hash, intactness flag, and a signed root statement. Useful as a contract test for any external verifier integrating with HiveWallet.
    Connector
  • Get AI-generated intelligence briefs for each supply chain dimension — energy, materials, transportation, macro, and manufacturing. Each brief provides a narrative analysis of current conditions, key drivers, emerging risks, and recommended watch items. These are not raw data — they are synthesized analytical summaries generated every hour from live data. Designed for decision-makers who need a quick read on each supply chain dimension. Returns structured briefs suitable for executive dashboards, email digests, or Slack channels.
    Connector
  • [BROWSE] Get full details for a specific listing by tokenId. Call this after list_drops to see what you are buying. Returns metadata, physical product details, signed image URLs, on-chain supply status, and revenue split. Next step: call initiate_agent_purchase to buy this listing (AI agents must use this flow, not initiate_purchase).
    Connector
  • Get detailed breakdown of supply chain disruption risk by category. Returns individual scores for each GDI pillar — Transportation (port congestion, border delays, freight weather), Energy (petroleum, natural gas, electricity, fuel prices), Materials (31 commodity prices with volatility), and Macro (Federal Reserve indicators, Producer Price Index). Each pillar includes its score, trend direction, and the specific data points driving the current reading. Essential for supply chain managers who need to diagnose which risk category is elevated and why.
    Connector
  • Get real-time supply chain disruption alerts from global news intelligence and event detection. Returns categorized alerts for port closures, trade policy changes, tariff actions, natural disasters, labor strikes, sanctions, commodity shortages, and weather disruptions. Each alert includes severity level, affected supply chain stage (sourcing, manufacturing, logistics, distribution), and risk score. Free tier returns critical-severity alerts only; paid tier returns all severities.
    Connector
  • Get active trade policy actions currently impacting supply chain risk — tariffs, sanctions, export controls, import restrictions, and regulatory changes. Unlike news alerts that expire after 72 hours, policy adjustments persist as long as the policy is in effect and continue to modify GDI risk scores. Each policy includes the affected GDI pillar, score modifier, effective date, and source event. Used by procurement teams navigating tariff exposure, compliance officers tracking sanctions, and supply chain strategists adapting sourcing to policy shifts.
    Connector