M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAsk Grok MCP ServerConsult Grok through xAI's metered API with exact model selection and no fallbackNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS55 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation12 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • MCP client users who want an independent Grok 4.7 opinion
  • Users who need exact control over model ID, reasoning effort, and output-token ceiling and accept metered billing
  • Developers who already hold an xAI API key or have the official Grok CLI installed
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users unwilling to pay metered API costs and looking only for free usage
  • Users needing automatic failover or multi-provider fallback — this server offers no harness or model fallback
  • Users who can neither provide XAI_API_KEY nor install grok-cli
  • Users who need fully offline or private local inference (a local provider would be a better fit)
  • Projects outside the NPM ecosystem (e.g., pure Python/Go)
  • Environments without network access to deps.dev, OSV.dev, and the npm registry
  • Scenarios requiring maintenance by an official upstream vendor
Required permissions
  • Requires the XAI_API_KEY secret environment variable, used only for requests to https://api.x.ai
  • If the grok-cli harness is used, requires an installed and authenticated official Grok CLI
  • Launched as a stdio process by the local MCP client from the npm package @ask-llm/grok-mcp
  • Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
  • Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
Risks and side effects
  • The xAI API is metered and paid; prompt and response length directly affect cost, and ASK_GROK_MAX_OUTPUT_TOKENS only bounds accidental spend
  • XAI_API_KEY is a secret; if leaked, others could consume your quota
  • The server never falls back to another harness or model, so a misconfiguration causes failure rather than degradation
  • Grok's answers come from a third-party tool that is not an official xAI product; verify output accuracy yourself
  • Prompt content is sent to xAI's service, so treat sensitive code or data with care
  • Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
  • Depends on availability and accuracy of external services
  • Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
  • Third-party open source project, not officially maintained by NPM or Anthropic
Supported clientsClaude Code, Claude Desktop, Cursor, Codex, PiClaude Desktop, VS Code, Cursor
Tools119