Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldAxiom MCPShortlist candidateMCP Server for Splunk platformMCP100 Recommended
Task fit
Best for
  • Investigate and manage Axiom observability data, dashboards, monitors, and service maps
  • Axiom users who need to investigate and manage axiom observability data, dashboards, monitors, and service maps.
  • Security and operations investigation over authorized Splunk searches and platform objects.
Not ideal for
  • Write tools can create or change datasets, dashboards, monitors, and notifiers. Use least privilege. Do not attribute the archived legacy mcp-server-axiom repository's stars to the current hosted service.
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • Write tools can create or change datasets, dashboards, monitors, and notifiers. Use least privilege. Do not attribute the archived legacy mcp-server-axiom repository's stars to the current hosted service.
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

Axiom · Publisher source ↗

First-party MCP

ecosystem:splunk-platform · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
Shared repository stars

16

Shared repository stars (not MCP-specific) · checked 2026-10-20

Not documented
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth for the hosted MCP, or a personal access token plus organization ID.Splunk documents encrypted token handling and platform authentication for the managed MCP Server for Splunk Platform 2.0. No public-repository metric is required for this managed-service identity.
CostNo separate MCP fee is documented. Axiom has free and paid observability plans; account query/ingest/storage usage remains subject to the product plan and configured limits.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsHosted MCP access follows Axiom organization/role authorization. Axiom supports role-level query cost limits; local/token setups can use API-token limits.Splunk roles, capabilities, and tool-level configuration constrain searches and platform access.
Data handlingAxiom states tokens are not exposed to agents and access can be revoked. The reviewed MCP docs do not state a broader MCP-specific prompt/data retention policy.Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive monitoring & observability information.
Limitations
Tradeoffs
  • Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.
  • Search results may expose sensitive security and operational events; broad search roles should not be used.
Risk contextThe MCP can query telemetry and also create/update/delete datasets, dashboards, monitors and notifiers. Mis-scoped writes can alter production observability configuration and potentially increase query/usage cost.Search results may expose sensitive security and operational events; broad search roles should not be used. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-10-192026-09-05
Candidate evidence2026-10-202026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →