Developer · Remote MCP server
AnomalyArmor
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.anomalyarmor/armor-mcp- Version
- 0.6.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- PyPI
- Published
- 2026-04-18
- Updated
- 2026-04-18
- Publisher
- ai.anomalyarmor
- Namespace
- Namespace verified by the MCP Registry via the domain anomalyarmor.ai · how
- Website
- www.anomalyarmor.ai
- Repository
- github.com/anomalyarmor/agents (folder armor-mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.anomalyarmor.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | armor-mcp | 0.6.1 | stdio |
How to connect AnomalyArmor
AnomalyArmor is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.anomalyarmor.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Python package published to PyPI: armor-mcp version 0.6.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx armor-mcp. It reads the environment variable ARMOR_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"armor-mcp": {
"command": "uvx",
"args": [
"armor-mcp"
],
"env": {
"ARMOR_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Anirbanbasu PymcpPrimarily to be used as a template repository for developing MCP servers with FastMCP in Python, P… | Remote · HTTPLive check: ✗ no handshake |
| AnnoLocal-first HTML review, editing, and annotation for AI coding agents. | Local · stdio |
| anodizerRust release tooling - drop-in GoReleaser parity + Rust extras. | Local · stdio |
| Anomaly AIAI data analyst: ask about your Excel, CSV, GA4 or database data and get charts and dashboards back. | Remote · HTTPLive check: sign-in required |
| Ansvar: Threat IntelligenceCVE intelligence, STRIDE, OWASP test cases via Ansvar Gateway. Cited, OAuth + paid. | Remote · HTTPLive check: sign-in required |
| AntideployDeploy an app to Antideploy from a coding agent. No Dockerfile, no YAML, no cloud console. | Local · stdio |
| Antigravity LinkMCP server and OpenAPI-backed mobile companion for controlling Antigravity IDE sessions. | Local · stdio |
| Antigravityextensiongate MCPPaid remote MCP for Antigravity extension compatibility MCP, structured receipts, audit logs, and re. | Remote · HTTPLive check: ✗ no handshake |