ToolsMCP
AnomalyArmor
Listed in the official MCP Registry with a hosted streamable-http endpoint and an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- anomalyarmor.ai
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record. Install armor-mcp from pypi (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.6.1 · updated
- Official links
Publisher’s description
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.6.1, registry status active. 1 remote endpoint (streamable-http); 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- anomalyarmor.ai
- Version observed
- 0.6.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/ai.anomalyarmor%2Farmor-mcp/versions/0.6.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Investigate errors and incidents | Publisher description mentions “observability”, “alerts”. | No connection check or task run. Capability is as described by the publisher. | Rule observability matched: “observability”, “alerts”. Rule observability. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://mcp.anomalyarmor.ai/mcp(streamable-http)- Packages
armor-mcp(pypi, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
ai.anomalyarmor/armor-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.