"Understanding Code Execution in Programming" matching MCP servers:

Enables agents to interact with the Logflare API by writing JavaScript functions that run in a Vercel Sandbox, using three tools: search, execute_read, and execute_write.

MCP server that provides read-only analysis of Claude Code session transcripts, enabling queries about project activity, session details, and tool usage.

Maintenance, recovery, and observability for Claude Code. CLI + MCP server + dashboard.

Echo tool MCP server that extracts and logs W3C Trace Context from requests to verify propagation from Claude Code.

A Model Context Protocol server for Zoho Site24x7 that uses a JavaScript sandbox to execute API calls, enabling management of monitors, accounts, and MSP/BU tenancy through natural language.

Enables bounded, deterministic triage verdicts for server health, fleet status, and timeline investigation through a simulated execution-boundary MCP server.

Surface Claude Code token usage, estimated cost, and plan-limit status in any MCP client. Enables agents to query usage data from local logs and Anthropic API.

Claude Code token usage and cost visibility for MCP-capable agents.

Lets an assistant read recorded production AI agent runs — steps, model and tool calls with arguments, and outcomes — along with the findings of comparison runs that checked a prompt or model change against those recordings, and verify a signed evidence bundle offline with no account or network. It is strictly read-only: no tool starts a replay or comparison, so nothing can spend money or act without a person deciding.

Enables AI assistants to query and analyze AI agent sessions from observability providers like Shepherd (AIOBS) and Langfuse, allowing users to debug agent runs, compare sessions, track performance, and analyze LLM usage patterns.

Enables MCP clients to query and triage security findings published to BigQuery and correlate them with execution, sandbox, and diagnostic traces in Cloud Logging. Exposes tools, resources, and prompts for filtering issues by severity, status, repository, or CWE, retrieving patch diffs and verification results, and diagnosing why a remediation or verification run failed.

Enables AI agents to trace Python code execution in real time via PEP 669, exposing call trees, variable deltas, and async context through MCP tools.

Enables time-travel debugging for AI agent sandboxes using Firecracker microVMs, with tools for code execution, file operations, and VM snapshot/restore via MCP.

MCP servers for real-time development monitoring and interactive pair programming.

Read-only MCP server that surfaces UniFi network data from a UCG-Fiber console to Claude, enabling monitoring of hosts, sites, devices, clients, ISP metrics, and device stats via read-only API tools.

Enables live tracing and observability of MCP tool calls, persisting execution traces to MongoDB and streaming them in real time to a dashboard.

A local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.

An MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.

MCP-native agent evaluation and observability server. Log traces, evaluate output quality with 12 built-in rules (PII detection, prompt injection, cost thresholds), and track agent costs. Real-time dashboard, OTel-compatible spans. Self-hosted, MIT licensed.

Production-grade MCP Gateway in Go featuring dynamic OpenAPI tool registration, RBAC governance, in-flight PII/DLP redaction, and structured JSON audit logging.