Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ai-anomalyarmor-armor-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
MCP Server for GCP environment for interacting with various Observability APIs.
Enhanced MCP server for GitLab: group projects listing and activity tracking
Real-time GitHub Actions observability: DORA Metrics, Cost Analysis, CI/CD Health dashboards.
AI cost tracking: 11 tools for spend, budgets, and Claude Code + Cursor + Cline costs
MCP Security Weekly
Get CVE alerts and security updates for ai.anomalyarmor/armor-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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
| Skill | Description | Example |
|---|---|---|
/armor:start | Guided onboarding for new users | "Help me get set up" |
/armor:status | Health summary across all assets | "Is my data healthy?" |
/armor:connect | Connect a new data source | "Connect my Snowflake warehouse" |
/armor:monitor | Set up freshness and schema monitoring | "Monitor freshness for orders table" |
/armor:alerts | Query and manage alerts | "What alerts fired yesterday?" |
/armor:ask | Natural language Q&A about your data | "What tables contain customer data?" |
/armor:analyze | Trigger AI analysis | "Analyze the finance schema" |
/armor:quality | Data quality metrics and validity rules | "Add null check for customer_id" |
/armor:coverage | Monitoring coverage analysis | "What tables have no monitoring?" |
/armor:recommend | AI-driven monitoring recommendations | "What should I monitor?" |
/armor:tags | Asset tagging and classification | "Tag this table as PII" |
/armor:investigate | Root cause analysis | "Why is this table stale?" |
/armor:lineage | Data lineage exploration | "What depends on this table?" |
/armor:profile | Table profiling and stats | "Profile the orders table" |
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 acr