Borrowing it
Nothing to install: this file belongs to stat-guy/grok-search-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stat-guy/grok-search-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/stat-guy/grok-search-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/stat-guy/grok-search-mcp/claude-md)<a href="https://agentmods.dev/instructions/stat-guy/grok-search-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/stat-guy/grok-search-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.05777 | $0.05777 |
| Opus 5 | $0.02889 | $0.02889 |
| Sonnet 5 | $0.01155 | $0.01155 |
| Haiku 4.5 | $0.00578 | $0.00578 |
Grade A, and why
grok-search-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 974 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grok Search MCP Server - AI Assistant Implementation Guide
Overview for AI Assistants
This document provides comprehensive technical guidance for AI assistants to help users download, install, configure, and implement the Grok Search MCP server. The server enables sophisticated web search capabilities with both basic results and comprehensive analysis modes through xAI's Grok API.
Quick Reference
Installation Command
git clone https://github.com/stat-guy/grok-search-mcp.git
cd grok-search-mcp
npm install -g .
Claude Desktop Configuration
{
"mcpServers": {
"grok-search": {
"command": "npx",
"args": ["grok-search-mcp"],
"env": {
"XAI_API_KEY": "your-api-key-here"
}
}
}
}
Configuration File Locations
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Installation Instructions for Users
Step 1: Obtain xAI API Key
Guide users through these steps:
- Visit the xAI Developer Portal
- Create an account or sign in
- Navigate to API Keys section
- Generate a new API key
- Copy the API key (format:
xai-...)
Step 2: Installation (Recommended)
Direct users through the 3-step process:
git clone https://github.com/stat-guy/grok-search-mcp.git
cd grok-search-mcp
npm install -g .
This automatically:
- Downloads the latest version
- Installs dependencies globally
- Makes the command available system-wide
Step 3: Verify Installation
Guide users to test the installation:
npx grok-search-mcp --help
Success indicator: If you see "Grok Search MCP Server v1.0.0" help text, installation is ready!
Alternative: NPX Usage
For quick testing without installation:
npx grok-search-mcp
Step 4: Configure Claude Desktop
Help users locate and edit their Claude Desktop configuration:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 974 lines · 5,777 tokens per session scan A a5fa3c26790b
grok-search-mcp CLAUDE.md is an instructions file published in the GitHub repository stat-guy/grok-search-mcp (18 stars, last pushed 1y ago), licensed MIT. It adds 5,777 tokens to every session, about $0.0289 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.