Sumo Logic MCP Server

sumo-logic-mcp PyPI v1.0.0

Published by rajfirke — 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.

MCP server for Sumo Logic — 48 tools for log search, monitors, alerts, dashboards, collectors, metrics, and more

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 48

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

  • cancel_searchno sensitive capability
  • check_connectionno sensitive capability
  • create_dashboardno sensitive capability
  • create_hosted_collectorno sensitive capability
  • create_http_sourceno sensitive capability
  • create_monitorno sensitive capability
  • delete_collectorno sensitive capability
  • delete_dashboardno sensitive capability
  • delete_monitorno sensitive capability
  • disable_monitorno sensitive capability
Show 38 more tools ↓
  • enable_monitorno sensitive capability
  • get_account_usageno sensitive capability
  • get_active_alertsno sensitive capability
  • get_alert_detailsno sensitive capability
  • get_collectorno sensitive capability
  • get_content_by_pathno sensitive capability
  • get_dashboardno sensitive capability
  • get_folderno sensitive capability
  • get_lookup_tableno sensitive capability
  • get_metric_metadatano sensitive capability
  • get_monitorno sensitive capability
  • get_monitor_historyno sensitive capability
  • get_monitor_statusno sensitive capability
  • get_personal_folderno sensitive capability
  • get_search_resultsno sensitive capability
  • get_search_statusno sensitive capability
  • get_sourceno sensitive capability
  • list_collectorsno sensitive capability
  • list_dashboardsno sensitive capability
  • list_field_extraction_rulesno sensitive capability
  • list_fieldsno sensitive capability
  • list_ingest_budgetsno sensitive capability
  • list_lookup_tablesno sensitive capability
  • list_metric_definitionsno sensitive capability
  • list_metric_namespacesno sensitive capability
  • list_monitorsno sensitive capability
  • list_partitionsno sensitive capability
  • list_rolesno sensitive capability
  • list_sourcesno sensitive capability
  • list_usersno sensitive capability
  • query_metricsno sensitive capability
  • resolve_alertno sensitive capability
  • search_logsno sensitive capability
  • search_monitorsno sensitive capability
  • update_collectorno sensitive capability
  • update_dashboardno sensitive capability
  • update_monitorno sensitive capability
  • validate_queryno 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
v1.0.0 latest A 99/100 0 1.13.0 2026-08-25

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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sumo-logic-mcp/badge.svg)](https://mcptrustchecker.com/registry/sumo-logic-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/sumo-logic-mcp"><img src="https://mcptrustchecker.com/registry/sumo-logic-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sumo-logic-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 sumo-logic-mcp --online --registry pypi

Use the free API → How scoring works

More in Web, Search & Scraping