PAGES
← all tools
◆ MCP Servers & Tooling

mcp-security

secops-soar-v0.2.0 open-source

Free plan: not checked yet · Open source: yes

MCP servers connecting AI clients to Google Security Operations, Threat Intelligence, SOARSOARSecurity orchestration, automation and response, coordinating incident workflows across tools. Playbooks can gather evidence, assign work or carry out approved response actions., and Security Command Center APIs.

What you can do now

Checking Plays…

Summary

mcp-security is an open-source MCP-tooling server that gives AI clients access to Google SecOpsSecOpsThe practice of merging security and IT operations teams so that threat detection, response, and infrastructure management share the same workflows, giving cyber tools a single pipeline from alert to remediation., Threat Intelligence, SOAR, and Security Command Center APIs, with no licence cost. It runs as separate local packages through uv or pip, or through a managed remote server, using Google authentication; blue-team practitioners can select only the services their workflows need. Its README presents it as an MCP interface for Claude Desktop and the Cline VS Code extension rather than a standalone SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents., with tools for UDM and event searches, detection-rule exclusions, and SOAR integrations. Ongoing releases add capabilities and authentication options.

MCP servers connecting AI clients to Google Security Operations, Threat Intelligence, SOAR, and Security Command Center APIs.

How mcp-security helps

Which security events in my Google SecOps environment match an investigation timeframe or query?

searches UDM records and events through Google SecOps and returns results scoped to the supplied time range; the answer is limited to data available through the authenticated SecOps service

Which detection-rule exclusions are affecting my SecOps detections?

retrieves and manages exclusions for detection rules, showing the exclusions available to the authenticated SecOps account and allowing authorized changes

What threat intelligence is available about an indicator or threat relevant to my investigation?

queries Google Threat Intelligence through the selected MCP service and returns the intelligence exposed for that indicator or threat; coverage depends on the account and service data

What cloud security risks are reported for my environment?

accesses findings and risk information from Security Command Center and presents what that service returns for the authenticated cloud environment

What response actions or integrations can I use for an incident?

connects an AI client to Google SecOps SOAR and its configured integrations so it can inspect or invoke the response capabilities exposed by the authorized SOAR account; available actions depend on that account's integrations and permissions

all 6 features, with the evidence for each →

Languages

Not documented

Features

6 capabilities

Built from mcp-security's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What mcp-security offers you

  • MCP server1

All capabilities 6 capabilities
MCP server connectivity for Google Security products Provides MCP servers that connect AI clients to Google Security Operations, Google Threat Intelligence, SOAR, and Security Command Center APIs. 5 other sources

Also counts toward: MCP server

Log parser enumeration Allows practitioners to list the available log parsers in the SecOps service. 1 release · first seen Aug 2026
Detection rule exclusions management Enables practitioners to create, update, and manage exclusions for detection rules in the SecOps service. 1 release · first seen Mar 2026
Service account authentication Supports service account credentials as an authentication option for connecting to the SecOps service. 1 release · first seen Feb 2026
MCP server execution mode selection Allows practitioners to choose between remote and local execution when running MCP server skills. 1 release · first seen Feb 2026
UDM and event search Search UDM records and events within the SecOps service, with support for scoped time-range queries via custom start and end time parameters. 1 release · first seen Jan 2026

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for mcp-security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail mcp-security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

7 entries

  1. November 20262
  2. August 20261
  3. March 20261
  4. February 20262
  5. January 20261
    Show

    7 entries

    Project health

    Issue, contributor and maintainer activity in google/mcp-security, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 59% of issues opened, last 12 months
    5. Median time to close 374 days first maintainer reply 17 days
    6. Open backlog 24 of 70 issues ever filed
    1. Issues opened / month 0 · 1 communitymaintainers
    2. Open backlog 24
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • features 4%
    • other 96%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Ships a vulnerable library

    What its latest release locks, checked against known advisories.

    google-cloud-aiplatform 1.97.0 in its run-with-google-adk image

    high

    mcp-security secops-v0.7.1 builds its run-with-google-adk image from run-with-google-adk/requirements.txt, which locks google-cloud-aiplatform 1.97.0. That version has GHSA-wh2j-26j7-9728.

    Fixed in google-cloud-aiplatform 1.133.0. No mcp-security release includes it yet.

    GHSA-wh2j-26j7-9728 advisory Checked Nov 20 against mcp-security secops-v0.7.1

    We check the lockfiles its release builds images from: 1 Python. Go modules, other lockfiles and vendored code aren't checked.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.