"Spring Boot" matching MCP servers:

Enables read-only access to JavaMelody monitoring data from one or more Java web applications, covering HTTP/SQL/Spring counters, JVM and thread snapshots, and database reports. Users can query several configured microservices from a single server process and inspect what is slow or failing without opening the JavaMelody dashboard.

An MCP server for managing MCP server registries with health checks, duplicate detection, and configuration portability. It helps prevent MCP sprawl by tracking server health, identifying overlapping tools, and generating portable configurations for different clients.

Enables MCP-aware AI agents to query the local machine's health over stdio, retrieving CPU, memory, disk, and load-average metrics along with boot time and the top processes by CPU usage. It gives coding agents a structured, protocol-standard way to answer questions like whether it is safe to run a build or what is currently consuming resources.

Provides unified AI agent observability including tracing, cost tracking, performance monitoring, anomaly detection, and audit trails via MCP.

MCP server for writing structured traces, spans, and decisions, enabling observability and EU AI Act traceability compliance for AI agent tasks.

Provides read-only access to OpenClaw and Codex operational data like status, tasks, sessions, logs, and Git changes. Ensures safety via redaction, allowlists, and bounded outputs.