AnomalyArmor
PYPI · ARMOR-MCP · 2 COMPONENTS · SCANNED SEP 20
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 113 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5788 tokens (~101/item across 57 items; 53 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 53 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AnomalyArmor MCP server?
AnomalyArmor runs locally as a PyPI package, launched with uvx armor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · armor-mcp
claude mcp add ai-anomalyarmor-armor-mcp -- uvx armor-mcp
{
"mcpServers": {
"ai-anomalyarmor-armor-mcp": {
"command": "uvx",
"args": [
"armor-mcp"
]
}
}
} {
"servers": {
"ai-anomalyarmor-armor-mcp": {
"command": "uvx",
"args": [
"armor-mcp"
]
}
}
} codex mcp add ai-anomalyarmor-armor-mcp -- uvx armor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-anomalyarmor-armor-mcp": {
"type": "local",
"command": [
"uvx",
"armor-mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-anomalyarmor-armor-mcp --command uvx --arg armor-mcp
mcp_servers:
ai-anomalyarmor-armor-mcp:
command: "uvx"
args: ["armor-mcp"] {
"McpServers": {
"ai-anomalyarmor-armor-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"armor-mcp"
]
}
}
} assistant mcp add ai-anomalyarmor-armor-mcp -t stdio -c uvx -a armor-mcp
{
"mcpServers": {
"ai-anomalyarmor-armor-mcp": {
"command": "uvx",
"args": [
"armor-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/armor-mcp@0.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
setup_freshness Setup Freshness ~182
Create freshness monitoring for one or more tables. Use explore to find table paths, recommend_freshness for suggested intervals.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset UUID (from list_assets) |
| check_interval | string | – | How often to check: "5m", "15m", "30m", "1h", "3h", "6h", "12h", "1d", "1w" |
| expected_interval_hours | – | – | Hours until stale (required for explicit mode) |
| freshness_column | – | – | Column to check (auto-detected if not provided) |
| monitoring_mode | string | – | "auto_learn" (recommended, learns thresholds) or "explicit" |
| table_path | – | – | Single table path (e.g., "public.orders") |
| table_paths | – | – | Multiple table paths for bulk setup (overrides table_path) |
No output schema declared.
No examples provided.
trigger_asset_discovery Trigger Asset Discovery ~63
Start schema discovery for an asset. Discovers all schemas, tables, columns, and metadata. Runs as background job. Use job_status() to track progress, then explore() to browse results.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Asset UUID (from list_assets) |
No output schema declared.
No examples provided.
update_alert Update Alert ~178
Update an alert's lifecycle status. Use list_alerts to find alert IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| action_category | – | – | For resolve/dismiss: reran_job, updated_sql, rolled_back, false_positive, expected_behavior, code_change, other |
| alert_id | string | yes | Alert UUID (from list_alerts) |
| duration_hours | integer | – | Snooze duration in hours, 1-720 (default 24). Only for status="snoozed". |
| notes | – | – | Optional notes explaining the status change |
| root_cause_category | – | – | For resolve/dismiss: pipeline_failure, schema_change, data_source_issue, configuration_error, expected_behavior, code_change, infrastructure, unknown |
| status | string | yes | New status: "acknowledged", "resolved", "dismissed", or "snoozed" |
No output schema declared.
No examples provided.
What is the AnomalyArmor MCP server?
AnomalyArmor is an MCP server listed in the public MCP registry as ai.anomalyarmor/armor-mcp. Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality. This page covers its PyPI package (armor-mcp).
Is the AnomalyArmor MCP server safe to use?
AnomalyArmor scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AnomalyArmor MCP server expose?
AnomalyArmor exposes 53 tools: get_alerts_summary, list_alerts, list_inbox_alerts, update_alert, list_alert_rules, and 48 more. Their descriptions and schemas cost roughly 5,496 tokens of context every time the server is loaded.
Is the AnomalyArmor MCP server still maintained?
AnomalyArmor is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AnomalyArmor MCP server under?
AnomalyArmor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.