com.fidacy/ai-agent-firewall vs Symantec Endpoint Detection and Response (on-premises) AIops
com.fidacy/ai-agent-firewall is an MCP server published by fidacy.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Symantec Endpoint Detection and Response (on-premises) AIops is an MCP server published by AIops-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.fidacy/ai-agent-firewall |  Symantec Endpoint Detection and Response (on-premises) AIops |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.1 Downloads/month (npm): 5 434 Downloads/week (npm): 1 658 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.24.13 Downloads/month (npm): 5 434 Downloads/week (npm): 1 658 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.fidacy/ai-agent-firewall | Symantec Endpoint Detection and Response (on-premises) AIops |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-03 | Not published |
| Where it runs (differs) | On your machine (@fidacy/mcp) | On your machine (symantec-edr-aiops) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/lucaslubi/fidacy-mcp | github.com/aiops-tools/symantec-edr-aiops |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-06 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.fidacy/ai-agent-firewall
Every agent action watched, every money-moving one gated, every verdict independently verifiable.
Symantec Endpoint Detection and Response (on-premises) AIops
Governed Symantec on-prem EDR — 20 MCP tools, read-only with audit.
How to run each
com.fidacy/ai-agent-firewall As a local MCP server: npm package
claude mcp add --env "FIDACY_ENGINE_API_KEY=<YOUR_FIDACY_ENGINE_API_KEY>" --transport stdio ai-agent-firewall -- npx -y @fidacy/mcpRequires: FIDACY_ENGINE_API_KEY (secret)
Symantec Endpoint Detection and Response (on-premises) AIops As a local MCP server: PyPI package
claude mcp add --transport stdio symantec-edr-aiops -- uvx symantec-edr-aiopsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Symantec Endpoint Detection and Response (on-premises) AIops publish no settings it asks for, so we do not compare settings.
What it can do: com.fidacy/ai-agent-firewall · What it can do: Symantec Endpoint Detection and Response (on-premises) AIops · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.