Grok FAF
NPM · GROK-FAF-MCP · SCANNED SEP 20
Persistent project context for xAI Grok. IANA-registered .faf format.
Available components
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 Security92
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 119 of 120 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- Dependency health was assessed across the 119 of 120 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 30 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 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 1428 tokens (~95/item across 15 items; 12 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the Grok FAF MCP server?
Grok FAF runs locally as an npm package, launched with npx -y grok-faf-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 · grok-faf-mcp
claude mcp add one-faf-grok-faf-mcp -- npx -y grok-faf-mcp
{
"mcpServers": {
"one-faf-grok-faf-mcp": {
"command": "npx",
"args": [
"-y",
"grok-faf-mcp"
]
}
}
} {
"servers": {
"one-faf-grok-faf-mcp": {
"command": "npx",
"args": [
"-y",
"grok-faf-mcp"
]
}
}
} codex mcp add one-faf-grok-faf-mcp -- npx -y grok-faf-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"one-faf-grok-faf-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"grok-faf-mcp"
],
"enabled": true
}
}
} openclaw mcp add one-faf-grok-faf-mcp --command npx --arg -y --arg grok-faf-mcp
mcp_servers:
one-faf-grok-faf-mcp:
command: "npx"
args: ["-y", "grok-faf-mcp"] {
"McpServers": {
"one-faf-grok-faf-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"grok-faf-mcp"
]
}
}
} assistant mcp add one-faf-grok-faf-mcp -t stdio -c npx -a -y grok-faf-mcp
{
"mcpServers": {
"one-faf-grok-faf-mcp": {
"command": "npx",
"args": [
"-y",
"grok-faf-mcp"
]
}
}
} 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.
- 20 Sept 26 −3
- Known CVEs: pass → partial ▼ security
- Dependency health: 0.86 → partial functional
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.90 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/grok-faf-mcp@1.10.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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/postinstall.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 119 packages
| Packages resolved | 119 |
|---|---|
| Stale | 37 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
faf_get_orchestration_policy ~130
Introspect the effective orchestration policy WITHOUT running the orchestrator. Returns `{ tier, thresholds, source, overrides_applied }` — what aggressiveness tier the next `faf_orchestrate_recommendation` call would use, and whether it came from defaults or a `.faf:orchestration:` override. No drift detection, no signals, no receipt — pure introspection. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Optional explicit `.faf` file path or project directory (supports ~). When omitted, the live process cwd is searched for project.faf / .faf. |
No output schema declared.
No examples provided.
faf_init ~236
Create a project.faf — the IANA-registered context file (application/vnd.faf+yaml) that gives Grok persistent project DNA (stack, structure, intent) in one portable file, so an agent reads the whole project cold each session instead of re-discovering it. Writes project.faf to the target directory (created if missing) and refuses to overwrite an existing context file unless `force` is set. Run once at project start, or with `force` to regenerate, then call faf_score to check readiness. Returns a text confirmation with the written file path and the detected project type.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Absolute or ~-relative project directory to initialize; created if it does not exist. Defaults to the current working directory. |
| force | boolean | – | Overwrite an existing project.faf. Default false: if a context file already exists, faf_init refuses and leaves it untouched. |
| path | string | – | Alias for `directory`; takes precedence if both are supplied. |
| projectName | string | – | Project name used to resolve the directory via the Projects convention when no directory/path is given. |
No output schema declared.
No examples provided.
faf_orchestrate_recommendation ~112
Heavy orchestrator — given current substrate state, returns a structured recommendation about drift: which refresh to call (or `no_action`), why, how severe, and the underlying signals. ADVISORY ONLY — never auto-fires. Composes the full 1.5 substrate (drift detection · contradiction check · repeat-offender · take-a-hint · refresh history). Writes a recommendation receipt on every call (auditable trail, no silent decisions). Read-only WRT substrate state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
faf_score ~78
Score a project's AI-readiness 0–100% against the fixed 33-slot context model — how much project DNA an agent has before it has to guess. Deterministic: the same .faf always scores the same. Returns the score, tier, and per-slot breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | Include detailed breakdown and improvement suggestions |
No output schema declared.
No examples provided.
faf_sync ~71
Sync project.faf into your AI context files (CLAUDE.md, AGENTS.md, .cursorrules, GEMINI.md). Non-destructive: injects a structured .faf block at the top for fast machine reading and preserves your prose below. One source of truth, every tool kept current.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
faf_trust ~52
Validate a project.faf's structure and integrity — confirm the context file is well-formed and parses cleanly before an agent grounds on it. The pre-flight trust check: never build on a broken context layer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rag_cache_clear ~49
Clear the LAZY-RAG cache — drop all cached retrievals so the next rag_query rebuilds from source. Use when the underlying context has changed and you want fresh results instead of cached ones.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rag_cache_stats ~27
Get LAZY-RAG cache statistics - hits, misses, hit rate, cache size
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rag_query ~50
Ask a question with RAG-enhanced context from xAI Collections. Uses LAZY-RAG cache for 100,000x speedup on repeated queries.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Question to ask |
No output schema declared.
No examples provided.
refresh_blend ~269
Baked-in two-intensity refresh (Cmd+R / Cmd+Shift+R analog). Fires BOTH `refresh_faf` + `refresh_fafm` in one call. `mode: "blend"` (default) = light `.faf` + delta `.fafm` — the everyday re-ground. `mode: "nuke"` = light `.faf` + verbatim `.fafm` — the hard reload for polluted session memory. Intensity matches drift rate per layer.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | number | – | For refresh_faf: your last-known score (0-100). Drift delta reported if provided. |
| mode | string | – | 'blend' (Cmd+R analog, default) = .faf + .fafm delta. 'nuke' (Cmd+Shift+R analog) = .faf + .fafm verbatim. |
| path | string | – | For refresh_faf: project directory or .faf path (supports ~). |
| since | string | – | For refresh_fafm (delta mode only): ISO timestamp. Only facts modified after this. Ignored when mode=nuke (verbatim). |
| soul | string | – | For refresh_fafm: specific soul. Omit or 'default' for primary; 'all' for every soul. |
No output schema declared.
No examples provided.
refresh_faf ~114
Re-ground on the live .faf — re-read + re-score the current project DNA, report drift vs your last-known score, and return the fresh context. The explicit re-grounding primitive for long sessions: drift → refresh → re-grounded. Built for Grok, by request.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | number | – | Your last-known score (0-100). If provided, the drift delta is reported. |
| path | string | – | Project directory or .faf path (supports ~). Defaults to the session working directory. |
No output schema declared.
No examples provided.
refresh_fafm ~201
Reload the latest structured memory (`.fafm`) for one or more souls into the current session. Returns a stamped delta by default (added/updated facts since last refresh or a given timestamp). Use `verbatim: true` to receive the full current `.fafm` content instead. Read-only. Always returns a content hash + timestamp stamp. Complements `recall`, `load_soul`, and `etch` — does not replace them.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Optional ISO timestamp. Only return facts modified after this time. Ignored when verbatim=true. |
| soul | string | – | Specific soul to refresh. Omit or use 'default' for the primary memory layer. Use 'all' to refresh every available soul. |
| verbatim | boolean | – | If true, returns the full current .fafm content for the requested soul(s) instead of a delta. Use sparingly — deltas are preferred for normal operation. |
No output schema declared.
No examples provided.
What is the Grok FAF MCP server?
Grok FAF is an MCP server listed in the public MCP registry as one.faf/grok-faf-mcp. Persistent project context for xAI Grok. IANA-registered .faf format. This page covers its npm package (grok-faf-mcp).
Is the Grok FAF MCP server safe to use?
Grok FAF scores 82 out of 100 on VerifyMCP. 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 Grok FAF MCP server expose?
Grok FAF exposes 12 tools: faf_score, refresh_faf, refresh_fafm, faf_orchestrate_recommendation, faf_get_orchestration_policy, and 7 more. Their descriptions and schemas cost roughly 1,389 tokens of context every time the server is loaded.
Is the Grok FAF MCP server still maintained?
Grok FAF is still listed as active in the MCP registry. We last reached this channel on 20 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 Grok FAF MCP server under?
Grok FAF declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.