"Finding People on LinkedIn" matching MCP servers:

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

Provides structured MCP tools for local runtime observability and debugging of React Native/Expo apps on Android, enabling evidence-first diagnostics such as screenshots, UI trees, per-request network capture, performance metrics, and CDP-based console/heap/profiling exports.

Provides MCP tools to create and query SigNoz trace funnels, enabling agents to measure their own step conversion rates from within the agent loop.

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.

Tells an agent what went wrong with its own Ollama calls, in sentences with the fix: lost prompt cache and where the prompt stopped matching, context overflow, a model running partly on CPU, tool schemas crowding the prompt. Also the last turn in numbers and which local models fit in video memory. Local, read-only, nothing leaves the machine.

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 coding agents to read performance findings from sixty, get detailed evidence for each finding, and close or resolve them with descriptions, while also checking service telemetry and providing installation instructions.

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 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.

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.

Enables AI agents to raise and resolve incidents in ITOC360, triggering escalation policies that page on-call responders and closing alerts when problems clear.

An on-call agent for data incidents, built on a bio-inspired context protocol. It triages data quality and freshness issues using DataHub, computing severity, blast radius, and ownership from the catalogue before generating prose.

An MCP server that provides monitoring tools for Codex agents, allowing them to create and wait on conditions using commands, log files, file events, and custom probes, replacing polling loops with event-driven blocking.

An MCP server that exposes GPU-accelerated anomaly detection to AI assistants via the Model Context Protocol. Provides two MCP tools: waveguard_scan (send training + test data in one call, returns per-sample anomaly scores and top explanatory features) and waveguard_health (check API and GPU status). Works on time series, JSON, numbers, text, and images — fully stateless.

Enables agents to check whether an execution trace contains the evidence needed for post-hoc causal reconstruction, retrieve individual requirement details, and list evidence requirements per failure class over MCP stdio. It works on files, directories, or inline JSON locally and never transmits or persists data.

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.