# aos-standard/mcp-agent-health [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/aos-standard/mcp-agent-health  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aos-standard-mcp-agent-health

## Description
MCP Agent Health Reporter — advisory agent health scan under AOS discipline (manifest, services, immune loop, evidence). Stdio MCP: mcp-agent-health. Install: pip install mcp-agent-health==0.3.1 · PyPI

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-agent-health": {
    "command": "uvx",
    "args": ["mcp-agent-health"]
  }
}
```

## Documentation

## What aos-standard/mcp-agent-health does

The aos-standard/mcp-agent-health MCP server reports on agent health before deployment. Its scope is defined by AOS discipline and covers four areas named by the project: the agent manifest, services, immune loop, and evidence. The available material describes the tool as an advisory reporter, so its output should be treated as guidance for reviewing an agent rather than as a stated deployment gate or runtime monitoring system.

This makes the project relevant when an agent needs a structured health review before it is released. The repository does not describe unrelated functions such as application observability, infrastructure monitoring, issue tracking, or automated remediation. Its stated purpose remains focused on validating agent health under the AOS model.

## How it works

The aos-standard/mcp-agent-health MCP server is provided as a stdio MCP. In that operating mode, an MCP client launches the local server process and communicates with it through standard input and output. The supplied description identifies the stdio server as `mcp-agent-health`.

The scan is organized around the four AOS-related subjects listed in the project description: manifest, services, immune loop, and evidence. The available README excerpt does not define the individual checks, result schema, severity levels, input format, or whether findings can be modified through MCP. Those details should be confirmed in the package documentation or the referenced agent card before building automation around its output.

## Setup and configuration

Install the published package with the command below:

```bash
pip install mcp-agent-health==0.3.1
```

The project points users to `packaging/README.md` for MCP client configuration. That file is not included in the supplied material, so the exact client configuration format, executable invocation, and required command-line arguments cannot be established here. The repository also links to a PyPI project, a catalog entry, and an agent card at `packaging/agent_card.json`.

No environment variables, API keys, service credentials, or external account requirements are specified in the provided README excerpt. Do not assume that additional configuration is unnecessary until the package and client-configuration documentation have been checked.

## Tools and capabilities

The stated capability is an advisory agent health scan. Its review scope includes:

- Checking the agent manifest as part of the AOS health review
- Reviewing declared or relevant services within that health model
- Including the immune loop in the health assessment
- Considering evidence during pre-deployment validation
- Exposing the reporter through the stdio MCP interface

The material does not list individual MCP tool names, parameters, return fields, or client-specific setup examples. As a result, this listing cannot confirm the exact tool call used to start a scan or retrieve its report.

## Limitations and notes

The aos-standard/mcp-agent-health MCP server is described as advisory, and the source material does not promise automatic fixes, continuous monitoring, deployment blocking, or compliance certification. It should therefore be evaluated as a pre-deployment reporting component. The excerpt also does not state a license, supported MCP clients, authentication method, environment variables, or compatibility guarantees. Those fields require confirmation from the repository’s packaging files or fuller documentation.

## Getting started with this aos-standard/mcp-agent-health MCP server
Always refer to the official documentation for the most accurate and up-to-date information.

_Full upstream README: https://allmcps.com/mcp/aos-standard-mcp-agent-health/readme_