io.github.Lykhoyda/ask-grok
NPM · @ASK-LLM/GROK-MCP
Consult Grok through xAI's metered API with exact model selection and no fallback
Available components
Last scanned (9 hours ago)
Scores higher than 87% of npm servers
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 38 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 456 tokens (~114/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@ask-llm/grok-mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask-grok ~277
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.7; CLI default: grok-4.7; 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.7 on xai-api or grok-4.7 on grok-cli; Ask LLM never rewrites or falls back fr… |
| prompt | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| harness | string | – | – |
| model | string | yes | – |
| provider | string | yes | – |
| reportedModel | string | – | – |
| response | string | yes | – |
| sessionId | string | – | – |
| usage | object | – | – |
No examples provided.
get-usage-stats ~81
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| byModel | object | yes | – |
| byProvider | object | yes | – |
| fallbackCount | number | yes | – |
| totalCachedTokens | number | yes | – |
| totalCalls | number | yes | – |
| totalDurationMs | number | yes | – |
| totalInputTokens | number | yes | – |
| totalOutputTokens | number | yes | – |
| totalThinkingTokens | number | yes | – |
No examples provided.
ping ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| harness | string | – | Harness whose exact model catalog should be listed |
| message | string | – | A message to echo back without contacting a provider |
No output schema declared.
No examples provided.
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.
npm · @ask-llm/grok-mcp
claude mcp add lykhoyda-ask-grok -- npx -y @ask-llm/grok-mcp
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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 425 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 5 November 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.