
AnomalyArmor
ai.anomalyarmorPublished by anomalyarmor.aiOfficial publisherv0.6.1Updated Oct 24, 2026
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
Overview
Lets an assistant query and manage AnomalyArmor data-warehouse observability: alerts, freshness, schema drift, quality rules, and lineage.
- What you can do
- Connects an MCP client to an AnomalyArmor account through 50+ tools covering warehouse health and briefings, alerts and incidents, assets, freshness schedules, schema monitoring, data-quality metrics and validity rules, alert destinations, lineage, tags, and async jobs. Read tools list and summarize alerts, freshness, drift, and quality; mutating tools create or update rules, schedules, metrics, assets, and destinations. Natural-language Q&A and AI analysis are also available, with long-running work returned as pollable job IDs.
- When to use it
- Use it when a team already monitors its data warehouse with AnomalyArmor and wants an assistant to triage alerts, check freshness or schema drift, inspect lineage, or adjust monitoring rules in conversation instead of through the web UI.
- Requirements
- Either the hosted remote endpoint over Streamable HTTP with OAuth 2.1, or the local armor-mcp package (PyPI, stdio) run with uvx or pip. The local option needs an AnomalyArmor API key supplied as the ARMOR_API_KEY environment variable or in the local config file, plus network access to the AnomalyArmor service.
Installation
In SourceWeft
- Open AnomalyArmor in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.anomalyarmor%2Farmor-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"anomalyarmor": {
"type": "http",
"url": "https://mcp.anomalyarmor.ai/mcp"
}
}
}README
armor-mcp
[PyPI] [License: MIT] [MCP] [Glama]
The AnomalyArmor MCP server lets AI assistants (Claude Code, Cursor, Claude Desktop, any MCP client) interact with your data warehouse through 50+ structured tools: query alerts, monitor freshness, investigate schema drift, configure validity rules, and trace lineage in natural language.
- Homepage: https://www.anomalyarmor.ai
- Docs: https://docs.anomalyarmor.ai/integrations/mcp-server
- Server card: https://www.anomalyarmor.ai/.well-known/mcp/server-card.json
- Status: Production. Versioned MCP protocol
2025-06-18. OAuth 2.1 + API key auth.
Two ways to connect
Remote (recommended)
The server is hosted at https://mcp.anomalyarmor.ai/mcp (Streamable HTTP transport). First call opens a browser for OAuth; the token is cached for ~12h.
Claude Code
Cursor
Add to ~/Library/Application Support/Cursor/mcp.json (macOS), ~/.config/Cursor/mcp.json (Linux), or %APPDATA%\Cursor\mcp.json (Windows):
Any MCP client
Local (API key)
Use when the remote server isn't reachable or when you want no third-party dependency.
Install
Configure
Get an API key from Settings → API Keys at https://app.anomalyarmor.ai.
Or persist to ~/.armor/config.yaml:
Wire to a client
Tools
53 tools across 8 categories. Every tool ships with MCP ToolAnnotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint: false) so hosts can decide when to auto-confirm.
Health & Briefings
Alerts & Incidents
Assets
Freshness
Schema Monitoring
Data Quality (Metrics & Validity)
Destinations & Routing
Intelligence, Lineage, Tags, Jobs
Full descriptions, parameter schemas, and example prompts: https://docs.anomalyarmor.ai/integrations/mcp-server.
Tool safety conventions
Hosts respect the annotations:
Multi-tenancy
The OAuth token (or API key) is scoped to the user's company. You cannot impersonate another tenant. Don't fabricate company_id arguments.
Async jobs
trigger_asset_discovery, generate_intelligence, and metric captures return a job_id. Poll with job_status(job_id) rather than re-triggering.
Discovery surfaces
Development
License
MIT — see LICENSE.
Source: armor-mcp/README.md at commit 74fed02
Tools
0Version history
1- v0.6.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts