"How to create draft emails using Gmail's support agent class" matching MCP servers:

A read-only MCP server exposing SLURM, GPFS, Prometheus (node exporter + DCGM GPU metrics) and generic Elasticsearch exploration as diagnostic tools for LLM-based HPC support assistants.

Registers a set of inert, tempting decoy tools with any MCP-capable client so that any call from a hijacked or prompt-injected agent instantly raises an alert with full attack context and a per-call trace token. Also plants worthless canary tokens in honeypot files that trigger zero-false-positive leak alerts when they surface in agent output, files, or outbound requests.

MCP server exposing AI agent observability tools: list, inspect, and deterministically replay recorded agent execution traces for debugging failures.

Analyzes AI agent traces to diagnose failures, score performance, and provide actionable fixes using tools like judge_trace and trace_breakdown.

Exposes rate-limit and usage data for AI coding agent CLIs as MCP tools, enabling querying of usage snapshots and reset times.

Enables AI agents to self-report every tool call, token usage, decision, and session grade into a local SQLite store, so users can trace execution, audit reasoning, and see per-session costs in a local dashboard. Also supports proxy mode to intercept and trace MCP tool invocations for agents that cannot self-report.

An MCP server that provides append-only, tamper-evident local receipts for AI agent actions, capturing command executions, outputs, and handoff evidence.

Local-first observability for AI agent stacks. Provides MCP tools for agents to check health, shadow configs, and burnout metrics proactively.

Enables AI apps to inspect and manage a NextDNS account in plain language — profiles, analytics, query logs, blocklists, security and parental control settings — with every change saved and reversible via undo. It runs self-hosted on your own computer or server, keeps per-profile read/write/hidden permissions, and requires double confirmation for deletions or overwrites.

Provides cost analysis of AI agent usage by previewing scrubbed metadata before upload and analyzing spend, cache-hit rates, and waste recovery through a local or remote server.

MCP server for AI agent observability, providing trace and span logging, search, latency/tokens/cost metrics, and anomaly detection using an in-memory buffer.

Enables AI agents to manage prompts and sessions via the ai-agent-logs API, with tools for health checks, login, listing/creating prompts, and retrieving sessions.

Tracks AI agent token usage and spending in real time, with budget alerts, per-task cost breakdown, and a visual dashboard.

Unified MCP safety server that detects prompt injection (75 patterns), scans LLM outputs for leaked secrets/PII, enforces API cost budgets, and creates signed audit trails. Zero ML dependencies, pure Python.

Enables agents to report and query performance metrics to build a community-driven quality database for MCP tools. This server helps agents discover and select the most reliable tools based on success rates and user-reported quality scores.

Enables recording and querying MCP tool call traces, including latency, failures, and token costs, per agent run.

Enables local-first observability for MCP agent workflows by recording tool calls, prompts, latency, and token usage in a local SQLite database, and provides tools for inspecting, comparing, exporting, and generating dashboards from traces.

An MCP server that exposes Estuary Flow pipeline operations as typed tools, enabling agents to inspect pipeline health, publish captures and materializations, edit/restart tasks, and read landed documents via tool calls.

MCP server that provides structured audit logging for AI agent repair tasks via tools to start, record, end, query, and export event traces, with JSONL persistence and SDK integration.

An intelligent triage layer for Cloud Security Posture Management (CSPM). It ingests raw vulnerability and misconfiguration findings from tools like Trivy or Wiz, deduplicates overlapping issues, and uses a rules-based scoring engine (with an optional LLM integration) to output a prioritized, highly actionable ticket list.