Skip to main content
Glama
341,200 tools. Last updated 2026-07-30 10:26

"A server for finding information about Flutter" matching MCP tools:

  • Explain what a flagged issue means, why it matters, and what to do. Every explanation also states what the check genuinely cannot determine -- for example, that detecting an open Telnet port does not prove the password is still the factory default. Args: finding_id (str): the id from a previous response. response_format (ResponseFormat): 'markdown' or 'json'. Default 'markdown'. Returns: str: In markdown mode: severity, the affected device, what the finding means, what to do about it, and the limits of the check. In json mode: { "finding": { ... }, # same finding schema as scan_network "device": { ... } | null # the affected device, if any } Examples: - Use when: "Why is that a problem?" after a scan flagged something - Use when: "Explain telnet_exposed:a4:cf:12:34:56:78" - Don't use when: the user wants the device overview - use edgedefense_get_device_detail Error Handling: If the id does not match, returns the list of currently available finding ids so the right one can be selected immediately.
    Connector
  • Submit an integration or staking inquiry on behalf of a user. All submissions are routed to Everstake's sales team via Pipedrive CRM. Use when a user expresses intent to integrate with Everstake, explore staking services, or request more information about products. Collect required fields (first_name, last_name, work_email) conversationally and gather optional fields where available. The lead_source field is set automatically by the server — do not ask the user for it. IF Submission fails, you can try contacting Everstake via form at https://everstake.one/contact-us
    Connector
  • Analyze a server response from authorized probing for information leakage, fingerprinting signals, and exploitation opportunities scoped to the authorized engagement. Accepts raw HTTP response headers and body (paste from Burp, curl, or any HTTP client) and returns structured findings grouped by category. Each finding includes: what was detected, why it matters for an authorized tester, how a defender detects misuse, and recommended remediation. Identifies version disclosures, stack traces, debug headers, internal paths, JWT/cookie patterns, CORS misconfigurations, and other common leakage patterns. Use as the bridge between recon/probing output and the methodology and payload tools.
    Connector
  • Get descriptive project information about a coin: description, links, team and tags. Use for 'tell me about Uniswap', 'what is this project'. Does NOT include price; for price and market cap use getTickersById. Read-only; coinId is a canonical id (resolve with resolveId). No API key required.
    Connector
  • Keyword search WITHIN a single episode's transcript. Returns matching chunks with surrounding context. Use instead of get_transcription when the user asked about a specific topic — server does this faster + cheaper on context.
    Connector
  • 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

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.
    Last updated
    6
  • A
    license
    A
    quality
    F
    maintenance
    A real-time server that provides Flutter/Dart documentation and pub.dev package information to AI assistants, ensuring they generate accurate and up-to-date Flutter code.
    Last updated
    8
    73
    MIT

Matching MCP Connectors

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

  • Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…

  • Get detailed information about a specific ad request, including pool selections if targeting mode is manual.
    Connector
  • Price out emptying a chain's native gas balance to exactly zero: how much actually arrives, the full fee breakdown, and whether the balance is even large enough to be worth recovering. Returns a quote ID; quotes expire after about 60 seconds. Executing the sweep needs the wallet's signing key, which this hosted server does not hold - use the @zerodust/mcp-server package or the SDK for that.
    Connector
  • 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
  • Returns public details for a single open job by ID. Use this tool after search_jobs when the user wants more information about one specific job.
    Connector
  • Get detailed information about a specific institutional investor by their SEC CIK number. Returns the institution name, total AUM, number of holdings, and filing history. Use get_institutions first to find the CIK for an institution.
    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
  • Record that the page is no longer there (article unpublished, link dead), or put it back live with archived false. Nothing is deleted: the line stays, and so does the history, because "they talked about us from March to July" is information. A page taken down stops counting as a presence on that source. Only take down after actually re-reading the address and finding it gone.
    Connector
  • Find info about notable/historic landmarks, towns, and remarkable sites near a coordinate. USE FOR: - "What's near Predjama Castle?" - "Notable landmarks around Ljubljana center" - "Tell me about places near 46.05, 14.51" - Finding historic, cultural, or geographic summaries for an entire area at once. - DO NOT iterate over the results to query individual items again. - One call is sufficient to answer the user's broad geographic inquiry. Combine the results into a single comprehensive summary for the user immediately. NOT FOR: directions, finding specific cafes/shops, raw geocoding.
    Connector
  • Retrieve detailed information about a specific campaign including its status, budget, participants, and delivery metrics.
    Connector
  • Get estimated delivery time, free shipping threshold, and carrier information for a specific country. Use this when a customer asks about shipping costs or delivery times to their location.
    Connector
  • Submit a field report about an MCP server you have actually used (what worked, what failed, surprising behavior). Reports are quarantined for human review and never auto-published.
    Connector
  • Get metadata and details for a specific FRED series. Returns comprehensive information about a series including its title, frequency, units, seasonal adjustment, source, and date range. Use this to understand what a series measures before pulling observations. Args: series_id: FRED series identifier (e.g. 'UNRATE', 'GDP', 'CPIAUCSL').
    Connector
  • Query vulnerabilities for multiple packages in one call — the primary tool for dependency audits, SBOM scanning, and lockfile triage. Pass an array of {name, ecosystem, version} tuples (up to 1000). Each entry in the response corresponds positionally to the input. Each finding includes CVE aliases for chaining to nist-nvd-mcp-server for CVSS scoring.
    Connector