mcp-scalyr-dataset
Related Servers
Alternatives to mcp-scalyr-dataset
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only querying and server-side reduction of VMware Aria Operations for Logs (vRealize Log Insight) 8.18.x data, including event aggregation with spike detection, message signature grouping, and capped raw log search.MIT
- AlicenseNot gradedqualityBmaintenanceProvides governed MCP tools for querying optionally restricted Microsoft Sentinel/Log Analytics tables and optional Defender XDR hunting data, retrieving incidents and entities, and—for agent identities only—adding attributed incident comments, with Entra ID authentication, KQL validation, rate limits, and redacted audit logging.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables governed, read-only investigations of Amazon Athena access logs by searching exact user, IP, or correlation indicators and summarizing activity by correlation ID, with parameterized queries, validation, and result limits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to ask Purple AI hunting questions, run PowerQueries over the Singularity Data Lake, and read alerts, vulnerabilities, misconfigurations and asset inventory from a SentinelOne console, plus VirusTotal and public CVE lookups. It is read-only and accepts per-request console credentials, making it stateless and multi-tenant.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables analytics agents to run validated read-only SQL against a warehouse API with enforced row limits, required JSON responses, and secret-safe audit metadata.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and investigate logs and metrics in the OpenObserve open source edition through read-only tools for stream inspection, SQL log searches, field-value lookups, context queries, and PromQL metric queries. It exposes no tools that modify data or configuration, relying on authenticated OpenObserve user permissions as the real authorization boundary.1MIT
TDQS
Scored across 4 tools
The four tools map to reasonably distinct jobs: facet discovery, volume counting, raw event retrieval, and aggregation. There is mild overlap — count_logs and power_query can both produce counts, and power_query can filter the same data search_logs filters — but the descriptions explicitly steer callers (e.g. 'not for dumping raw messages — use search_logs').
Three of four names follow a clean verb_noun pattern (search_logs, count_logs, list_log_facets) with a shared 'logs'/'facet' vocabulary. power_query deviates by naming a product feature rather than an action, but it is still readable and unambiguous.
Four tools is a lean but defensible surface for a log-query server covering discovery, counting, search, and aggregation. It sits slightly on the thin side — there is no schema/field-listing tool to support exploration — but no tool feels redundant.
Search, count, facet discovery, and aggregation with a continuation_token cover the core query workflow. However, list_log_facets requires already knowing a field name, and there is no way to enumerate fields/datasets or to fetch a specific event or surrounding context, which will cause dead ends for an agent exploring an unfamiliar dataset.