Skip to main content
Glama
625,810 tools. Updated 2026-10-01 00:43

"How to check console logs and network activity" matching MCP tools:

  • Retrieves browser console logs (errors, warnings, GM_log) to diagnose script runtime errors after reload. Saves full log to .customaise/console-context.json, or returns inline without a file.
    MIT
  • Fetch a chronological recent-activity feed for EVM, Solana, Bitcoin, or Hyperliquid networks. Use it to see what happened on a network in a given timeframe, with paging and filters for incident triage.
    MIT
  • Summarize a specific contract's recent on-chain activity: interaction volume, unique callers, and event logs. Get a contract-level snapshot of what the contract has been doing on an EVM network.
    MIT
  • Retrieve browser console logs from Webvizio tasks when the task prompt lacks sufficient information for execution, providing additional context to complete development tasks.
    MIT
  • Get a Substrate or Polkadot activity snapshot for a chosen window: see event, call, and extrinsic counts plus top event and call names.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables querying and analyzing Tenable Vulnerability Management audit logs, including activity summaries, API key usage, and anomaly detection through MCP tools.
    6
    1
    MIT

Matching MCP Connectors

  • The official MCP Server from Mia-Platform to interact with Mia-Platform Console

  • DeFi Protocol Activity Index -- quantitative on-chain activity metric from DefiLlama data

  • Retrieve full details of a resource by ID, including files, workflows, agents, and activity logs.
    MIT
  • Retrieve blockchain event logs by specifying network, contract addresses, and topic filters. Access detailed on-chain activity data for analysis and monitoring purposes.
    MIT
  • Clear console, JS errors, and network logs to reset browser state before navigating to a new page, ensuring fresh data in subsequent inspections.
    MIT
  • Collect a full debugging snapshot of the browser: current URL, title, console logs, alerts, and network requests with headers/body. Filter by URL, method, or console type to pinpoint issues.
    MIT
  • Check UniFi console authentication and reachability, including transport, site, and Network version. Run first when a tool is missing to diagnose an older console or configuration error.
    MIT
  • Retrieve bounded browser event logs (console, page errors, network, failed requests) for a specific page, using checkpoints to capture complete evidence.
    Apache 2.0
  • Fetch a complete bug-report record by ID: description, console logs, network requests, screenshot, classification, fix history, and a paste-ready fix packet. Read-only; reporter identities are excluded.
    MIT
  • Retrieve recent events from the unified buffer of server stdout/stderr and browser console/network/pageerror. Filter by source, stream, or regex, and tail incrementally since a sequence number.
    MIT
  • Check network dependencies by retrieving all referencing WiFi broadcasts, firewall policies, and port profiles. Use this before deleting a network to avoid breaking configurations.
    MIT
  • Retrieve browser console messages (log, warn, error) to debug JavaScript errors and inspect application logs. Filter by level or clear the buffer after reading.
    MIT
  • Retrieve the recorded timeline of the active pair-debugging session, including console logs, network requests, errors, navigations, and actions. Use this to diagnose issues when something appears wrong.
    MIT