A
licenseNot graded
qualityC
maintenanceEnables AI assistants to query multi-cloud cost and usage data through a uniform read-only toolset, including cost summaries, trends, budgets, forecasts, and optimization recommendations.
MIT
Log10x MCP Server
Officialby log-10x
Related Servers
Alternatives to Log10x MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides seamless access to Kibana and Periscope logs through a unified API with KQL and SQL querying, AI-powered log analysis, and support for searching across 1.3+ billion logs in 9 indexes.1-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying of AWS cloud spending and Amazon Bedrock usage logs, with detailed breakdowns by day, region, service, instance type, user, and model, including cross-account cost retrieval.-
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing AI logs through tools like listing logs, retrieving jobs, and performing AI-powered chat queries. Also provides access to gateway security reports and guardrail testing.-
- AlicenseAqualityCmaintenanceLets AI agents query, manage, and operate their LLM observability data directly from the conversation. Provides 87 tools for cost analysis, alerting, anomaly detection, and runtime control gates.87236 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to query OriginChain's telemetry agent for log patterns, semantic incident analysis, distributed traces, service graphs, and read-only SQL queries over telemetry data.104 npmMIT
TDQS
A4/5.0
Scored across 56 tools
Disambiguation3/5
Many tools share closely overlapping purposes: top_patterns / whats_changing / whats_new / pattern_diff / pattern_trend all answer 'what are my patterns doing over time', resolve_batch and extract_templates both run local templatization, and the three retriever_query/series/query_status and three poc_* tools require careful reading to distinguish. The descriptions compensate heavily with explicit 'call this first', 'do NOT call for X, use Y' routing cues, which keeps it workable but demonstrates the boundaries are genuinely fuzzy.
Naming Consistency4/5
Every tool carries the log10x_ prefix and uses snake_case throughout with a mostly predictable verb_noun pattern (resolve_batch, discover_env, configure_engine, retriever_query). A few noun-only names (doctor, start, baseline, savings) are minor deviations that don't break readability.
Tool Count2/5
56 tools is far beyond what a coherent set should expose; many are narrow single-purpose helpers (env_validate, env_diff_vs_envvars, compile_status, query_status, retriever_probe) that could be consolidated into parameterized tools. The sheer breadth makes the surface hard to navigate even though each tool is individually motivated.
Completeness4/5
Coverage is impressively broad for the domain: discovery, install, POC (networked/local/fenced), pattern analytics, mitigation, retrieval, cross-pillar correlation, and auth are all present. Gaps are minor, e.g. there is no obvious tool for deleting/cleaning up an offload bucket or revoking credentials, but agents can work around these.
Maintenance
ActivityActive
ResponsivenessNo issues