Skip to main content
Glama
Sign In
debaditya-mohankudo

Splunk Intelligence MCP Server

by debaditya-mohankudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Splunk Intelligence MCP Server

No user-submitted related servers found.

    Related Servers

    • Splunk MCP for SOC Operations

      DeepTempo
      A
      license
      B
      quality
      D
      maintenance
      Enables AI-driven SOC investigations by providing automated Splunk querying, threat intelligence enrichment, and response actions through natural language. Includes tools for IP pivoting, lateral movement detection, and label harvesting.
      31
      1
      Apache 2.0

    • MCP Server for Splunk

      deslicer
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to interact seamlessly with Splunk environments through 20+ tools for search, analytics, data discovery, administration, and health monitoring. Features AI-powered troubleshooting workflows and supports multiple Splunk instances with production-ready security.
      57
      27
      Apache 2.0

    • Splunk Enterprise MCP Server

      nks1097
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to connect to Splunk Enterprise through 100 typed, audited tools for SPL searches, SOC operations, threat hunting, dashboards, knowledge management, and cluster diagnostics, with read-only safeguards and human confirmation for destructive actions.
      100
      Apache 2.0

    • REA

      mohammed123-code
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents (and a matching CLI) to inspect native binaries, JavaScript/Electron apps, .NET assemblies, Go/Rust/WASM artifacts, EVM bytecode, SQLite databases, recorded crashes, and websites without source code, explaining how features work and returning the evidence and limitations behind each conclusion. Analysis runs locally, using optional Hopper, Ghidra, or IDA providers for native targets.
      510,255 npm
      MIT

    • Darknet MCP

      Vinaysati
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to investigate domains, emails, IPs, hashes, URLs, onion addresses, Bitcoin addresses and CVEs across 68 tools spanning 19 threat-intelligence and dark-web source categories, returning bounded evidence with provenance, coverage and explicit skipped, errored or inconclusive checks. It also ships a local investigation dashboard for running combined lookups, reviewing source readiness and downloading JSON reports.
      68
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly distinct: investigate_start initiates, get_findings retrieves current findings, hint injects hints, lsp_call_chain traces code, pause halts, query_examples provides example queries, submit_report submits a report. There is slight overlap between get_findings and the findings returned by investigate_start, but descriptions clarify the different usage points.

    Naming Consistency3/5

    All tools share the 'splunk__' prefix and use lowercase with underscores, but the verb-noun pattern is inconsistent: 'get_findings' (verb_noun), 'hint' (just verb), 'investigate_start' (verb_noun), 'lsp_call_chain' (noun_verb), 'pause' (verb), 'query_examples' (noun_verb), 'submit_report' (verb_noun). Some tools are single words, others have multiple parts, but overall readable.

    Tool Count4/5

    Seven tools is a reasonable count for a focused investigation server. It covers the core workflow without being excessive. A few more could be added (e.g., listing past investigations), but the current count is appropriate.

    Completeness4/5

    The tool set covers the main investigation lifecycle: start, get findings, inject hints, trace code, pause, get examples, and submit report. Missing operations like direct arbitrary SPL querying are partially handled through investigate_start and submit_report queries. Overall, it's well-scoped with minor gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources