AnomalyArmor Agents
AI skills and MCP server for AnomalyArmor data observability. Monitor data quality, detect schema drift, and manage alerts directly from Claude Code, Cursor, or any MCP-compatible AI tool.
接入你的智能体
發布者自己的 URL。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
https://mcp.anomalyarmor.ai/mcp上方的 Claude 按鈕會開啟 Claude,並填好名稱和 URL。你仍需在那裡確認。
claude mcp add --transport http ai.anomalyarmor-armor-mcp https://mcp.anomalyarmor.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.anomalyarmor-armor-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.anomalyarmor.ai/mcp" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
AI skills and MCP server for AnomalyArmor data observability. Monitor data quality, detect schema drift, and manage alerts directly from Claude Code, Cursor, or any MCP-compatible AI tool.
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
這個伺服器在連線時會要求你登入。你的代理會處理這個步驟。
Version: 0.6.0 | Tools: 52 consolidated MCP tools | Skills: 14 slash commands
# Install the plugin
claude plugin marketplace add anomalyarmor/agents
claude plugin install armor@anomalyarmor
# Or via skills.sh
npx skills add anomalyarmor/agents
Then use skills like:
/armor:status - Check data health/armor:alerts - View and manage alerts/armor:recommend - Get AI monitoring recommendations/armor:ask - Ask questions about your dataAdd to your MCP configuration (Claude Code, Cursor, etc.):
{
"mcpServers": {
"armor": {
"command": "uvx",
"args": ["armor-mcp"]
}
}
}
ARMOR_API_KEY env var or create ~/.armor/config.yaml:api_key: aa_live_your_key_here
Tools follow a consolidated pattern: one tool per domain handles multiple operations via an action parameter, reducing context window usage while maintaining full functionality.
health_summary() - Overall data health across all assetsget_todays_briefing() - Daily AI briefing with alerts, freshness, and coverage gapsget_alerts_summary() - Alert counts by severity and statuslist_alerts(status, severity, asset_id, from_date, to_date) - Query alerts with filterslist_inbox_alerts(status, limit) - Unresolved alerts inboxupdate_alert(alert_id, action, ...) - Acknowledge, resolve, snooze, or comment on alertsget_alert_trends(period) - Alert trends over timeget_alert_history(alert_id) - Full history for a specific alertlist_alert_rules(asset_id, is_active) - List configured rulescreate_alert_rule(asset_id, rule_type, ...) - Create new alert rulemanage_alert_rule(rule_id, action, ...) - Update, delete, enable/disable, or duplicate ruleslist_assets(source, asset_type, search) - List monitored assetscreate_asset(name, source_type, connection_config) - Create data sourcemanage_asset(asset_id, action, ...) - Update, delete, test connection, or trigger discoverytrigger_asset_discovery(asset_id) - Start schema discoveryget_freshness_summary() - Freshness overview across all assetscheck_freshness(asset_id, table_path) - Check specific table freshnesssetup_freshness(asset_id, table_path, check_interval, ...) - Create freshness schedulelist_freshness_schedules(asset_id) - List configured schedulesmanage_freshness_schedule(schedule_id, action, ...) - Update, delete, pause/resume schedulesget_schema_summary() - Schema drift overviewlist_schema_changes(asset_id, severity, from_date, to_date) - List detected changescreate_schema_baseline(asset_id, description) - Create baselineenable_schema_monitoring(asset_id, schedule_type, notify_on) - Enable monitoringdisable_schema_monitoring(asset_id) - Disable monitoringget_schema_monitoring(asset_id) - View current monitoring configdry_run_schema(asset_id, schedule_type) - Test schema monitoring before enablingget_metrics_summary(asset_id) / list_metrics(asset_id) - View metricscreate_metric(asset_id, metric_type, table_path, ...) - Create row count, null rate, or custom metricmanage_metric(metric_id, action, ...) - Update, delete, capture, or view snapshotsget_validity_summary(asset_id) / list_validity_rules(asset_id) - View validity rulescreate_validity_rule(asset_id, rule_type, table_path, ...) - Create validity rulemanage_validity_rule(rule_id, action, ...) - Update, delete, check, or view resultscreate_referential_check(asset_id, ...) - Create cross-table referential checkmanage_referential(check_id, action, ...) - List, delete, run, or view resultslist_destinations(destination_type) - List alert destinations (Slack, email, webhook)setup_destination(destination_type, ...) - Create Slack channel, email, or webhook destinationmanage_destination(destination_id, action, ...) - Update, delete, test, enable/disablemanage_rule_destinations(rule_id, action, ...) - Link/unlink destinations to alert rulesget_coverage(asset_id) - Coverage tier and score for an assetmanage_coverage(asset_id, action) - Get next steps or apply recommended monitoringrecommend(asset_id, recommendation_type) - AI recommendations for freshness, metrics, coverage, or thresholdsask_question(asset, question) - Natural language Q&Agenerate_intelligence(asset) - Trigger AI knowledge base generationget_lineage(asset_id, depth, direction) - Data lineage graphjob_status(job_id) - Check async job statuscreate_tag(asset_id, name, object_path, ...) - Create and assign tagslist_tags(asset_id) / apply_tags(asset_id, ...) - List and apply tagsget_api_key_info() - View current API key details and permissionsUser: Is my data healthy?
Your data health status:
- Overall: WARNING
- 3 unresolved alerts (1 critical, 2 warning)
- 2 stale tables (orders, customers)
- 1 unacknowledged schema change
- Coverage: 65% (Tier 2: Protected)
User: What should I monitor on my Snowflake warehouse?
Based on your table patterns and update frequency:
1. orders (high traffic) - Add freshness check (hourly), row count metric
2. customers (PII) - Enable schema drift monitoring, add null checks
3. payments (financial) - Add freshness + row count + validity rules
Want me to set these up? I can configure all three in one go.
User: What happened overnight?
Your daily briefing:
- 2 new alerts: orders table stale (6h), schema change in users
- Coverage improved: finance schema now at Tier 3 (Verified)
- Recommendation: 4 tables still have no monitoring. Run /armor:recommend.
User: Why is the orders table stale?
Investigation results:
- Last update: 6 hours ago (expected: hourly)
- Upstream dependency: raw_orders was last updated 8 hours ago
- Likely cause: upstream ETL job failed or delayed
- Impact: 3 downstream dashboards affected
Error: No API key configured
Solution: Set ARMOR_API_KEY environment variable or create ~/.armor/config.yaml
Error: MCP server 'armor' not found
Solution:
uvx --versionSolution:
claude plugin listSee AGENTS.md for development guidelines.
MIT License - see LICENSE
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
{ "mcpServers": { "ai.anomalyarmor-armor-mcp": { "url": "https://mcp.anomalyarmor.ai/mcp", "headers": {} } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 http 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:ARMOR_API_KEY。
AnomalyArmor 透過 HTTP 存取。
上次檢查時間:2026-11-12。 Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.