AnomalyArmor vs Ezstat MCP Server
A side-by-side look at the AnomalyArmor and Ezstat MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AnomalyArmor for monitoring work as a local process; choose Ezstat MCP Server for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AnomalyArmor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ARMOR_API_KEY.
Choose Ezstat MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
EZSTAT_API_KEY. - You want tools like
track_metric, ask_ezstat, read_stat.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 36/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ARMOR_API_KEY | EZSTAT_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View AnomalyArmor | View Ezstat MCP Server |
Tools & capabilities
AnomalyArmor tools
No tool names declared yet. Check the project README from the listing page.
Ezstat MCP Server tools 7
track_metricRecord a metric point your app "produced". Use this whenever the surrounding code emits a counter or gauge — e.g. on a page view, a successful checkout, or a measured latency. Counters are +N (default +1), values are gauges (e.g. 42.5 ms).ask_ezstatAsk a natural-language question about the account's metrics. This is the agent-read path: send a question like "what spiked yesterday?" or "compare signups vs cancellations last 7 days" and EzStat returns a grounded answer plus the underlying data it used.read_statRead a single stat: latest value, recent series, and basic summary (count/min/max/avg/sum). Use this for a structured read of one metric — prefer `ask_ezstat` for free-form questions over many stats.list_statsList the account's metrics — names and types. Call this first when you don't know what stats exist in the account.create_alertCreate an alert on a stat: webhook fires when the condition is met (above/below threshold, % change, heartbeat/missing data, sustained). Deliveries retry with backoff and carry a stable idempotency_key so receivers can dedup. The stat is referenced by NAME; it must already exist.list_alertsList the account's alerts: id, stat, condition, channel, enabled, last trigger time.delete_alertDelete an alert by id (see list_alerts).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AnomalyArmor
{
"mcpServers": {
"anomalyarmor": {
"command": "uvx",
"args": [
"armor-mcp"
],
"env": {
"ARMOR_API_KEY": "YOUR_ARMOR_API_KEY_HERE"
}
}
}
}
Ezstat MCP Server
{
"mcpServers": {
"ezstat-mcp-server": {
"url": "https://mcp.ezstat.dev"
}
}
}
Frequently asked questions
AnomalyArmor is categorized under Monitoring and uses a local stdio subprocess. Ezstat MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick AnomalyArmor for monitoring work and Ezstat MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AnomalyArmor has no declared pricing — check the project's own site. Ezstat MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add anomalyarmor and ezstat-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AnomalyArmor has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Ezstat MCP Server has 55/100 (Good) with 3 views, 0 installs and 0 GitHub stars.