# io.github.Lykhoyda/ask-grok (npm · @ask-llm/grok-mcp)

Consult Grok through xAI's metered API with exact model selection and no fallback

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@ask-llm/grok-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/lykhoyda-ask-grok/ask-llm-grok-mcp.md), [page](https://verifymcp.io/servers/lykhoyda-ask-grok/ask-llm-grok-mcp)

## Channel facts

- Registry: `npm`
- Package: `@ask-llm/grok-mcp`
- Version: `0.1.5`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 450 tokens (~112/item across 4 items; 3 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ask-grok" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.Lykhoyda/ask-grok MCP server?

io.github.Lykhoyda/ask-grok runs locally as an npm package, launched with npx -y @ask-llm/grok-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lykhoyda-ask-grok -- npx -y @ask-llm/grok-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "lykhoyda-ask-grok": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/grok-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lykhoyda-ask-grok": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/grok-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lykhoyda-ask-grok -- npx -y @ask-llm/grok-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lykhoyda-ask-grok": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ask-llm/grok-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lykhoyda-ask-grok --command npx --arg -y --arg @ask-llm/grok-mcp
```

### Hermes

```yaml
mcp_servers:
  lykhoyda-ask-grok:
    command: "npx"
    args: ["-y", "@ask-llm/grok-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "lykhoyda-ask-grok": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ask-llm/grok-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lykhoyda-ask-grok -t stdio -c npx -a -y @ask-llm/grok-mcp
```

### Other

```json
{
  "mcpServers": {
    "lykhoyda-ask-grok": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/grok-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 72, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 57, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.1.4 → 0.1.5

### 2026-09-12 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 56)

First indexed and scored.

## MCP tools (3)

### `ask-grok` (~271 tokens)

Send a prompt to Grok through either the supported xAI Responses API or Grok Build's headless CLI (default harness: xai-api; default API model: grok-4.6; CLI default: grok-build; reasoning effort: high). Requires XAI_API_KEY and can incur xAI API charges. Ask LLM never enables billing, priority processing, credits, overage, model substitution, or fallback. Returns the actual provider/model and usage through the standard structured AskResponse.

Input parameters:

- `harness` (string): Execution harness, kept separate from the Grok model selection: xai-api or grok-cli. Defaults to xai-api; no harness fallback is attempted.
- `model` (string): Exact model ID understood by the selected harness. Do not set unless the user explicitly requests one. Defaults to grok-4.6 on xai-api or grok-build on grok-cli; Ask LLM never rewrites or falls back…
- `prompt` (string, required): The question, code review request, or analysis task to send to Grok through the selected harness
- `reasoningEffort` (string): Reasoning depth: low, medium, high, xhigh. Defaults to high; this is a request parameter, not a model-name suffix.

Output parameters:

- `harness` (string)
- `model` (string)
- `provider` (string)
- `reportedModel` (string)
- `response` (string)
- `sessionId` (string)
- `usage` (object)

### `ping` (~67 tokens)

Verify Grok MCP configuration and list exact model IDs available to the configured xAI API key. Model discovery does not make a billed inference call.

Input parameters:

- `harness` (string): Harness whose exact model catalog should be listed
- `message` (string): A message to echo back without contacting a provider

### `get-usage-stats` (~81 tokens)

Get the current MCP server's session usage stats: total LLM calls, token totals (input/output/thinking/cached), wall time, and breakdowns per provider and per model. No data leaves your machine — counts are tracked in-memory for the lifetime of the server process. Returns both human-readable markdown and a structured JSON snapshot via outputSchema.

Output parameters:

- `byModel` (object)
- `byProvider` (object)
- `fallbackCount` (number)
- `totalCachedTokens` (number)
- `totalCalls` (number)
- `totalDurationMs` (number)
- `totalInputTokens` (number)
- `totalOutputTokens` (number)
- `totalThinkingTokens` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/lykhoyda-ask-grok/ask-llm-grok-mcp#diagnostics

## Score history

- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 57
- 2026-09-12: 71
- 2026-09-11: 56

## Common questions

### What is the io.github.Lykhoyda/ask-grok MCP server?

io.github.Lykhoyda/ask-grok is an MCP server listed in the public MCP registry as io.github.Lykhoyda/ask-grok. Consult Grok through xAI's metered API with exact model selection and no fallback. This page covers its npm package (@ask-llm/grok-mcp).

### Is the io.github.Lykhoyda/ask-grok MCP server safe to use?

io.github.Lykhoyda/ask-grok scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.Lykhoyda/ask-grok MCP server expose?

io.github.Lykhoyda/ask-grok exposes 3 tools: ask-grok, ping, get-usage-stats. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.

### Is the io.github.Lykhoyda/ask-grok MCP server still maintained?

io.github.Lykhoyda/ask-grok is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.Lykhoyda/ask-grok MCP server under?

io.github.Lykhoyda/ask-grok declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@ask-llm/grok-mcp
- Socket report: https://socket.dev/npm/package/@ask-llm/grok-mcp
- Repository: https://github.com/Lykhoyda/ask-llm
- Changelog RSS feed: https://verifymcp.io/servers/lykhoyda-ask-grok/ask-llm-grok-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lykhoyda-ask-grok/ask-llm-grok-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lykhoyda-ask-grok/ask-llm-grok-mcp