Symantec Data Center Security AIops

io.github.AIops-toolsPublished by GitHub account AIops-toolsv0.1.0Updated Nov 6, 2026

Governed Symantec DCS operations — 35 MCP tools, read-only with audit.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Read-only MCP server and CLI exposing 35 governed tools for Symantec Data Center Security management status, assets, alerts, events, policies, reports, roles…

What you can do
  • Inspect management console status and server health
  • Browse and page through asset inventory, including asset errors
  • Review alerts, alert rules, events and policy violations
  • Read policies, reports, roles, users and syslog configuration
  • Every call is recorded as a local audit event
When to use it
Useful when an assistant needs to answer questions about a Symantec Data Center Security deployment — inventory, alerting, events, policy state or user and role setup — without granting it any ability to change configuration.
Requirements
Runs locally as a Python package (uvx or pip) over stdio. Needs a reachable management console HTTPS origin in SYMANTEC_DCS_URL, plus SYMANTEC_DCS_USERNAME and SYMANTEC_DCS_PASSWORD. Optional SYMANTEC_DCS_CA_BUNDLE, SYMANTEC_DCS_TIMEOUT and SYMANTEC_DCS_AIOPS_HOME. Desktop only.
Before you install
Requires console credentials in environment variables (SYMANTEC_DCS_USERNAME, SYMANTEC_DCS_PASSWORD); protect them and prefer a least-privilege account. Audit events are written locally under ~/.symantec-dcs-aiops/ by default. It is a community project, not affiliated with or endorsed by Broadcom or Symantec, and the README notes live behavior is unverified.

Installation

In SourceWeft

  1. Open Symantec Data Center Security AIops in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Symantec Data Center Security AIops

Independent audited MCP server, CLI and skill for management status, assets, alerts, events, policies, reports, roles, users and syslog. This initial release exposes 35 read-only tools. MCP and CLI call the same governed functions; API credentials remain in environment variables, TLS verification is on, and every call records a local audit event.

Community-maintained project. Not affiliated with or endorsed by Broadcom or Symantec; product names are their owners’ trademarks.

Configure

sh
export SYMANTEC_DCS_URL="..."export SYMANTEC_DCS_USERNAME="..."export SYMANTEC_DCS_PASSWORD="..."

SYMANTEC_DCS_URL must be the management console HTTPS origin (normally https://host:4443), without a path. Optional SYMANTEC_DCS_CA_BUNDLE points to a trusted CA bundle; SYMANTEC_DCS_TIMEOUT defaults to 30 seconds. Audit state defaults to ~/.symantec-dcs-aiops/ and can be relocated with SYMANTEC_DCS_AIOPS_HOME.

See the operations catalog for the complete tool list, scope and deferred operations.

Use

sh
uvx --from symantec-dcs-aiops==0.1.0 symantec-dcs-aiops status serveruvx --from symantec-dcs-aiops==0.1.0 symantec-dcs-aiops-mcp

Use assets with a sort key to page through inventory; inspect asset-errors, alert-rules, events and policy-violations before making conclusions. See verification for the exact evidence and unverified live behavior. No state-changing operations are exposed.

Source: README.md at commit 31074f6

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.1.0LatestNov 6, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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