grok-native-search-mcp@1.0.0
MCP server for Grok native Web Search, X Search, and Jina Reader web fetch
AI Security Review
scanned 3d ago · by lpm-firewall-aiSearch requests forward the user's xAI API key to a third-party gateway selected by default. The README discloses the gateway and the handoff occurs on a requested search, so this is suspicious rather than clearly malicious.
Decision evidence
public snapshot- The search handler sends XAI_API_KEY as a Bearer token in a POST request.
- Without XAI_BASE_URL, search requests go to aiapiv2.kamipon.com:442.
- The README documents that third-party gateway as the default.
- The key is sent when a search tool is used, not automatically during installation.
- The README identifies the gateway and describes XAI_API_KEY as for xAI or a compatible gateway.
- The manifest declares prepublishOnly running tests, with no install hook.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L24A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L24Findings
Affected versions and remediation
This report applies to grok-native-search-mcp@1.0.0.
See all versions of grok-native-search-mcp for other recorded verdicts.
- Review the evidence and your use of grok-native-search-mcp@1.0.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.