ooruby: verified AI agents and MCP servers

MCP Kql Server

AI-Powered MCP server for KQL query execution with Natural Language to KQL (NL2KQL) conversion, intelligent schema memory, RAG-enhanced context assistance, and semantic search capabilities

Not claimed by its maker. Is this yours? Prove it and answer the findings

Not yet tested

Command execution is bounded: inventory; python subprocess (tests/test_mcp_server.py:121); python subprocess (tests/test_mcp_server.py:147); python subprocess (tests/test_package.py:39); python subprocess (mcp_kql_server/kql_auth.py:58); An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

Everything. Treat it as you would software from anywhere else.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

AI-Powered MCP server for KQL query execution with Natural Language to KQL (NL2KQL) conversion, intelligent schema memory, RAG-enhanced context assistance, and semantic search capabilities

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 2.1.5, the file with digest sha256:a2d4d7558a4b29c5324e0c3a12d8f2946d95e53666d9ef144622ed4844616525, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.

How the rungs work

Adding it

Paste this into your client's MCP configuration.

{
  "mcpServers": {
    "mcp-kql-server": {
      "command": "uvx",
      "args": [
        "mcp-kql-server@2.1.5"
      ]
    }
  }
}

Or run it directly.

uvx mcp-kql-server@2.1.5

Pinned to 2.1.5, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

Where this came from

Registry: pypi
Package: mcp-kql-server
Version read: 2.1.5
Resolved: 2026-09-23

Open the source

Build provenance not checked yet. The repository above is the one the publisher declared on PyPI. Whether that registry holds a signed statement linking this release to it has not been looked up for this listing, so this page makes no claim either way.

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/mcp-kql-server)](https://ooruby.com/market/mcp-kql-server)

About this listing

Kind: MCP server
Category: Data & analytics
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-08-03

Similar MCP servers

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.