Skip to main content
Glama
466,528 tools. Updated 2026-08-19 16:56

"Information about network devices" matching MCP tools:

  • Retrieves the interactions between the query proteins. Use this method only when you specifically need to list the interactions between all proteins in your query set. If user asks for 'physical' or 'complex' use 'physical' network type. - For a **single protein**, the network includes that protein and its top 10 most likely interaction partners, plus all interactions among those partners. - For **multiple proteins**, the network includes all direct interactions between them. - If the user refers to "physical interactions", "complexes", or "binding", set the network type to "physical". - STRING does not store or report information about self-interactions/homomers; if asked, explain the limitation. If few or no interactions are returned, consider reducing the `required_score`. For large query sets (>50 proteins), consider increasing the `required_score` (e.g. ≥700) to focus on high-confidence interactions and avoid overly dense networks. - Expand the names of score sources: `nscore` (neighborhood), `fscore` (fusion), `pscore` (phylogenetic profile), `ascore` (coexpression), `escore` (experimental), `dscore` (database), `tscore` (text-mining)
    Connector
  • Performs **network clustering** on a STRING interaction network and returns both a **network image URL** and details about each detected cluster. Use the same parameters as in the network creation step to ensure consistency. If the network already contains disconnected subgraphs, the resulting number of clusters may differ from the requested value. Dashed lines represent connections between clusters, while solid lines indicate interactions within clusters. Notes: - For small queries (≤5 proteins), the `required_score` parameter is automatically lowered to 0. - If only a single cluster is produced, try increasing `required_score`, adjusting the inflation parameter, or switching to `kmeans` for small, highly interconnected networks.
    Connector
  • Returns a 0-100 Ethereum network sentiment score (composite z-scores of active addresses and transaction count vs 30-day baselines, daily since 2015) with per-component attribution, ETH network-context tiles, and methodology_version. Call when the user asks about Ethereum on-chain activity, ETH network demand heating up or cooling off, or address/transaction trends, or when timing launches, deployments, or gas-sensitive operations. Directional indicator, not a trading signal. Updates: daily.
    Connector
  • Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.
    Connector
  • Send the user's answer to a question the maker (vendor) asked about a UFP order — get_order_status surfaces an open question when one is waiting. Confirm the answer with the user before sending. The network relays it: the maker sees plain text from the network account with the user's contact details and links stripped, so never include emails, phone numbers, or URLs the answer depends on.
    Connector
  • Search FDA WARNING LETTERS — official enforcement letters FDA sends firms for violations (CGMP, adulterated/misbranded products, unapproved claims). Answers "FDA warning letters for <company>", "recent FDA warning letters about supplements/devices". Full-text search over ~3,600 letters (company names, subjects, products). Returns each letter's company, posted/issued dates, issuing FDA office, subject, and a link to the full letter text. Keyless, live from fda.gov.
    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

Matching MCP Connectors

  • FDA medical-device regulatory intelligence from keyless openFDA datasets.

  • MCP server for network documentation, generated by doc2mcp.

  • Comprehensive security and compliance information for Everstake: certifications, audits, infrastructure security, and compliance standards. Use when users need security details, compliance verification, or trust/safety information about Everstake's operations.
    Connector
  • Get detailed information about a specific ad request, including pool selections if targeting mode is manual.
    Connector
  • Get aggregate statistics about missions on the HomeVisto platform. Returns total counts, status breakdown, and average bounty information. Useful for understanding platform activity.
    Connector
  • Get information about the authenticated partner account. WHEN TO USE: - Checking current partner status and stats - Verifying API key is working - Getting partner account details RETURNS: - partner_id: Partner identifier - company_name: Registered company name - status: Account status (active, suspended, etc.) - device_count: Number of registered devices - total_impressions: Lifetime impression count - earnings: Earnings summary EXAMPLE: User: "What's my partner account status?" get_partner_info({})
    Connector
  • Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions.
    Connector
  • Bitcoin network hashrate level and trend. Takes no arguments. Returns { as_of, hashrate_eh (exahashes per second), pct_30d, pct_90d, why, disclaimer }. Example: {}. Information, not financial advice.
    Connector
  • Get one token's data and metadata by contract address on one network: multi-timeframe price and volume metrics, plus name, website, Twitter, and Telegram links, returned as a single token object. Read-only and keyless. Use for 'price and volume for 0x... on Base' or 'tell me about this token'. If you only have a symbol like WETH, call search first to resolve the address and network. For many tokens' prices at once use getTokenMultiPrices; for the pools holding this token use getTokenPools. Params: network (required slug); token_address (required contract address, e.g. 'JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN' on solana).
    Connector
  • Get the big picture for Bitcoin block, fee, and address activity over a recent or explicit window. COMMON USER ASKS: - Bitcoin network snapshot FIRST CHOICE FOR: - the big picture for Bitcoin right now WHEN TO USE: - You want the big picture for Bitcoin right now. - You want a network-level Bitcoin snapshot. - You care about block cadence, fees, SegWit/Taproot adoption, or activity metrics. DON'T USE: - You need raw transactions rather than network analytics. EXAMPLES: - Bitcoin network snapshot: {"network":"bitcoin-mainnet","timeframe":"1h"}
    Connector
  • Get detailed information about a domain you own, including auto-renew status, security lock, WHOIS privacy, and provider data.
    Connector
  • LAB tool — pure local expected-value calculator over a win-rate and average win/loss percentages. No network, no advice, 0 units. Feed a get_accuracy bucket win-rate (or a score_symbol band) to reason about expectation per trade.
    Connector
  • Get a structured pre-trade consensus signal for a sector and/or market regime. Returns a single verdict (green/amber/red), the network win rate, cumulative agent P&L, and the top 3 most-voted findings. Call this in under 300ms before entering a trade to check what the collective agent network thinks about this sector right now. No agent_id required — this is open-access intelligence.
    Connector
  • Returns information about how easy Fluentive is to set up and use. Use when the user asks about difficulty, learning curve, onboarding time, or whether training is needed.
    Connector
  • Check the current user's token status and account information. This tool retrieves information about: - User ID - Paid account status - Remaining generation tokens (for non-paid users) - Account validity Returns: A JSON string containing token status and account information
    Connector