Google Secops MCP Server

google-secops-mcp PyPI v0.7.0

Published by google — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 67

Each tool and what it can reach — statically extracted from the published source.

  • fetch_associated_investigationsingests untrusted input
  • activate_parserno sensitive capability
  • add_rows_to_data_tableno sensitive capability
  • compute_rule_exclusion_activityno sensitive capability
  • create_data_tableno sensitive capability
  • create_feedno sensitive capability
  • create_parserno sensitive capability
  • create_reference_listno sensitive capability
  • create_retrohuntno sensitive capability
  • create_ruleno sensitive capability
Show 57 more tools ↓
  • create_rule_exclusionno sensitive capability
  • create_watchlistno sensitive capability
  • deactivate_parserno sensitive capability
  • delete_data_table_rowsno sensitive capability
  • delete_feedno sensitive capability
  • delete_watchlistno sensitive capability
  • disable_feedno sensitive capability
  • do_update_security_alertno sensitive capability
  • enable_feedno sensitive capability
  • export_udm_search_csvno sensitive capability
  • find_udm_field_valuesno sensitive capability
  • generate_feed_secretno sensitive capability
  • get_available_log_typesno sensitive capability
  • get_curated_ruleno sensitive capability
  • get_curated_rule_by_nameno sensitive capability
  • get_curated_rule_setno sensitive capability
  • get_detection_ruleno sensitive capability
  • get_feedno sensitive capability
  • get_investigationno sensitive capability
  • get_ioc_matchesno sensitive capability
  • get_parserno sensitive capability
  • get_reference_listno sensitive capability
  • get_retrohuntno sensitive capability
  • get_rule_detectionsno sensitive capability
  • get_rule_exclusionno sensitive capability
  • get_security_alert_by_idno sensitive capability
  • get_security_alertsno sensitive capability
  • get_threat_intelno sensitive capability
  • get_watchlistno sensitive capability
  • ingest_raw_logno sensitive capability
  • ingest_udm_eventsno sensitive capability
  • list_curated_rule_set_deploymentsno sensitive capability
  • list_curated_rule_setsno sensitive capability
  • list_curated_rulesno sensitive capability
  • list_data_table_rowsno sensitive capability
  • list_feedsno sensitive capability
  • list_investigationsno sensitive capability
  • list_rule_errorsno sensitive capability
  • list_rule_exclusionsno sensitive capability
  • list_security_rulesno sensitive capability
  • list_watchlistsno sensitive capability
  • lookup_entityno sensitive capability
  • patch_rule_exclusionno sensitive capability
  • run_parser_against_sample_logsno sensitive capability
  • search_curated_detectionsno sensitive capability
  • search_rule_alertsno sensitive capability
  • search_security_eventsno sensitive capability
  • search_security_rulesno sensitive capability
  • search_udmno sensitive capability
  • test_ruleno sensitive capability
  • trigger_investigationno sensitive capability
  • update_curated_rule_set_deploymentno sensitive capability
  • update_feedno sensitive capability
  • update_reference_listno sensitive capability
  • update_rule_exclusion_deploymentno sensitive capability
  • update_watchlistno sensitive capability
  • validate_ruleno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.7.0 latest A 96/100 0 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/google-secops-mcp/badge.svg)](https://mcptrustchecker.com/registry/google-secops-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/google-secops-mcp"><img src="https://mcptrustchecker.com/registry/google-secops-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/google-secops-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan google-secops-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools