Advisory MCP health reporter that checks agent manifests, services, immune loops, and evidence before deployment.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Agent Health.
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.
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.
Install the published package with the command below:
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.
The stated capability is an advisory agent health scan. Its review scope includes:
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.
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.
Always refer to the official documentation for the most accurate and up-to-date information.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/aos-standard-mcp-agent-health)<a href="https://allmcps.com/mcp/aos-standard-mcp-agent-health"><img src="https://allmcps.com/api/badge/aos-standard-mcp-agent-health?style=directory" alt="MCP Agent Health on AllMCPs" /></a>