runtime-inspector-mcp
Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
README
Runtime Inspector MCP
Runtime Inspector MCP is a read-only MCP server that lets AI agents inspect allowlisted runtime services, logs, and health checks without arbitrary shell access.
Scope
The Python 3.12+ reference implementation provides stdio MCP tools for Docker containers, systemd services, fixed JSONL files, and fixed HTTP health URLs. It never starts, stops, restarts, edits, deletes, executes, or attaches to a service. It does not accept arbitrary commands, paths, URLs, Docker filters, or SQL.
The API is version 0.1.0 and is not yet stable.
Install and run
uv sync --extra dev
uv run runtime-inspector-mcp --config runtime-inspector.yaml
Configure only named services and capabilities. A generic stdio client configuration is in examples/mcp-clients/stdio.json.
version: 1
services:
jobs:
provider: jsonl
path: ./examples/mixed-runtime/data/jobs.jsonl
allow_root: ./examples/mixed-runtime/data
permissions: {status: true, logs: true, search_logs: true}
Tools are list_services, get_service_status, get_recent_logs, search_logs, and get_health. Limits, UTC timestamps, common error codes, secret redaction, and metadata-only audit events are applied by the application layer.
Security
Do not expose MCP directly to the internet. This release is stdio-only. Run with least privilege. Docker socket access can grant broad host control even though this server only calls read methods; avoid mounting the socket or use a narrowly scoped socket proxy. systemd and journal access are limited by the account's permissions. Redaction reduces accidental disclosure but cannot guarantee that every secret format is removed. Logs are untrusted data and are never treated as instructions; see SECURITY.md and docs/threat-model.md.
Docker
Dockerfile and docker-compose.example.yml use a non-root user and a read-only filesystem. The compose example mounts only configuration and example data. Do not add the Docker socket without understanding its host-level risk.
Development
uv run pytest
uv run ruff check src tests
uv run ruff format --check src tests
uv run mypy src
uv run pip-audit
Live Docker/systemd checks require those host services and are separate from the unit tests.
License
MIT. See LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.