Skip to main content
Glama
679,861 tools. Updated 2026-10-20 04:25

"A tool for inspecting and debugging Model Context Protocol (MCP) servers" matching MCP tools:

  • Discover available webhook tunnels to check their status, protocol, and creation time before inspecting requests.
    AGPL 3.0
  • Generate executable SQL from dbt model, test, and analysis files. Validate complex Jinja logic and macro usage by inspecting compiled output directly.
    Apache 2.0
  • Directly call an MCP tool for debugging raw input/output. Use only for diagnostics; normal operations should use execute_code.
    MIT
    Destructive
  • Record raw WAMP WebSocket frames and socket lifecycle events from the League Client into a chronological timeline for deep protocol diagnostics, connection-drop debugging, and message-flow analysis.
    MIT
    Destructive

Matching MCP Servers

Matching MCP Connectors

  • Retrieve device registry details including integration, manufacturer, model, and connections to identify network protocol and configuration entry for debugging or re-pairing.
    MIT
  • Retrieve full details for any OpenRouter model, including pricing, context limits, and description. Use this to evaluate model suitability or check specific model information.
    MIT
  • Summarize local GGUF or safetensors models: architecture, parameter count, quantization, context length, file size, tensor count. Reads only headers, so inspecting a 70GB model is instant.
    MIT
  • Retrieve live list of reachable Qwen models with id, label, capabilities, and context window to pick a model for Qwen coding tasks. Starts no task.
    MIT
  • List active Chrome DevTools Protocol debugging targets exposed by the League Client. Find target IDs and inspect renderer contexts before taking screenshots or tailing console/network.
    MIT
  • Get independent analysis from Codex, Grok, or DeepSeek for debugging, architecture evaluation, repository reasoning, and second opinions without modifying your workspace.
    MIT
  • Retrieve complete HTTP headers and context details for debugging, with sensitive values masked. Use this to troubleshoot issues by examining request metadata.
    Apache 2.0
  • Connect to any Chrome DevTools Protocol-compatible debugger (Node.js, Chrome, Edge) via WebSocket URL to start a new debugging session. Returns a session ID for all subsequent operations like breakpoints and variable inspection.
    Apache 2.0
  • Parse ASAN crash context to extract exception record, context record, and call stack when debugging AddressSanitizer-instrumented binaries.
    MIT
  • Filter and retrieve raw events by date, project, model, user, and status with pagination. Ideal for inspecting individual errors, user actions, or model behavior.
    MIT