"Exploring Research on MicroChannel Plates (MCPs)" matching MCP servers:

MCP server that diagnoses ML model regressions by correlating drift reports, eval runs, and deploy logs, providing evidence-cited incident reports through a set of investigation tools.

MCP server exposing qbit_manage's Web API as tools, so an LLM can read and manage a qbit_manage instance: run maintenance commands on qBittorrent torrents, manage config files, scheduler, logs, security settings, and system state.

A Model Context Protocol server for the AVEQ Surfmeter management API. It exposes typed tools for clients, measurements, anomalies, groups, ISPs, users, keys, capabilities, settings, license usage, and the built-in AI assistant.

MCP server for On-Call Health burnout analysis. Connects AI assistants to your on-call data for workload insights.

Connects AI assistants to the Vectra AI security platform to enable intelligent analysis of threat detection data and automated incident response workflows. It allows users to investigate threats, take response actions, and generate security reports using natural language.

Exposes a CognOS agent system as a machine-readable JSON graph, enabling Claude to get a full system snapshot and inspect node status, edges, and blocked nodes.

Enables querying and exploring KairosDB time-series data through natural language, including range/absolute queries, aggregations, last values, metric and tag listing, and health checks.

Read-only MCP server for exploring and searching OpenSearch clusters, enabling log analysis, index exploration, and query execution.

Enables MCP-compatible agents to interact with Grafana instances for searching, creating, and updating dashboards, exploring logs via Loki, querying datasources, managing alerts, incidents, and on-call shifts, and accessing observability data.

Enables querying and managing Azure Log Analytics workspaces using KQL (Kusto Query Language). Supports executing queries, managing saved queries, and exploring workspace tables and schemas with Service Principal authentication.

MCP server exposing rlg (RustLogs) log files as tools for on-call / SRE agent workflows. Three tools over JSON-RPC stdio — tail_log (last N events, filtered by level/target), filter_log (predicate filtering), summarize_errors (grouped error taxonomy). Pure Rust. MIT OR Apache-2.0.

Enables log analysis for Tenable Patch Management (SaaS and on-prem) by parsing, de-duplicating, and decoding server/client logs into structured verdicts, ranked issues, and known-issue fixes.

Enables an LLM agent to investigate a Kong Gateway through fourteen read-only, schema-validated tools and a deterministic diagnostic engine, so it can trace routes, services, plugins and upstream health and explain faults such as why authentication is failing on a path. Every fact comes from the gateway itself, and the model only selects tools and writes the evidence-backed explanation.

Enables interaction with Jira Service Management Operations alerts and on-call schedules, including searching alerts, reading notes and activity logs, acknowledging, closing, annotating, adding responders, and querying current and next on-call rotations.

Exposes live industrial IoT telemetry to any MCP client, streaming simulated sensor data from a fleet of machines and detecting anomalies, with the ability to inject faults on demand.

Enables agents to query GPU availability across SSH hosts, find free GPUs, list hosts, and inspect fleet status using only nvidia-smi on the remote side.

Enables a discovery subagent that performs docs research, logs triage, and codebase exploration, returning structured findings and specifying raw reads needed by the parent agent.

Enables AI agents to interact with Freeplay, an ops platform for AI engineering teams, to analyze production logs, identify quality issues, iterate on prompts and agents using real data, and run experiments before deploying.

Read-only AMD GPU monitoring for Claude on Linux — VRAM, temperature, clocks, power, and running ML processes via rocm-smi.

The logs of everything on one machine — app, build, GPU, containers, serial board, OS — interleaved in the order they happened, and readable by an agent. Read-only: it can tail, search and wait, and it cannot write, delete or configure anything.