Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Wolfe-Jam/gemini-faf-mcp

PYPI · GEMINI-FAF-MCP

Persistent project context for Google Gemini. Python/FastMCP. IANA-registered .faf format.

Available components

+15 this week 89 Trust /100

Last scanned (20 hours ago)

Scores higher than 92% of PyPI servers

Deprecated

This server is marked deprecated in the MCP registry.

Trust breakdown (7 categories)

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 Security91
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects starlette 0.52.1, reached via functions-framework > starlette. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 64 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Wolfe-Jam/gemini-faf-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 19 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 862 tokens (~71/item across 12 items; 12 tools + 0 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 2 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 24 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 21 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
Diagnostics

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 4 Nov 2026 · Analysed pypi/gemini-faf-mcp@2.5.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Wolfe-Jam/gemini-faf-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Wolfe-Jam/gemini-faf-mcp/.github/workflows/pypi.yml@refs/tags/v2.5.0
Rekor log index 1844929435
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:64c8a7c4627c99ac711b40592fefb278695a4d482661576e5ba2b8f8909cece7

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 10 findings
ID CVE Severity Vector Fix available
GHSA-82w8-qh3p-5jfq CVE-2026-54283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-86qp-5c8j-p5mr CVE-2026-48710 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-jp82-jpqv-5vv3 CVE-2026-54282 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wqp7-x3pw-xc5r CVE-2026-48818 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-x746-7m8f-x49c CVE-2026-48817 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-161 CVE-2026-48710 none yes
PYSEC-2026-2280 CVE-2026-48817 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-2281 CVE-2026-48818 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-248 CVE-2026-54282 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-249 CVE-2026-54283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 64 packages
Packages resolved 64
Stale 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~845 tokens

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 →

Tool Tokens
faf_about ~52

FAF format info — IANA registration, version, ecosystem. Returns metadata about the FAF format, server version, and available MCP bridges. Use this when users ask what FAF is or how it connects to other AI platforms.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

faf_agents ~84

Export and write AGENTS.md from a .faf file (non-destructive). Generates a universal agent context file (OpenAI Codex, Cursor, etc.) and injects it into AGENTS.md as a faf-managed block, preserving any existing content. Re-running updates the block in place — it never overwrites your file.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_auto ~101

Auto-detect project stack and generate/update a .faf file. Scans for package.json, pyproject.toml, Cargo.toml, go.mod, and other manifest files. Extracts language, framework, database, API type, and build tools from actual dependencies — no hardcoded defaults. Creates a new .faf if none exists, or fills empty slots in an existing one.

NameTypeReqDescription
directorystring––
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_context ~59

Get Gemini-optimized context from a .faf file. Returns the key sections an AI needs: project info, stack, instructions, and score. Use this to quickly understand a project without reading the full .faf structure.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_discover ~56

Find .faf files in the project tree by walking up from start_dir. Searches the current directory and parent directories for project.faf. Use this before faf_read to locate the file automatically.

NameTypeReqDescription
start_dirstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_gemini ~80

Export and write GEMINI.md from a .faf file (non-destructive). Generates Markdown with YAML frontmatter for Gemini CLI and injects it into GEMINI.md as a faf-managed block, preserving any existing content. Re-running updates the block in place — it never overwrites your file.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_init ~94

Create a starter .faf file with project name, goal, and language. Generates a valid FAF YAML file with all required sections. Will not overwrite an existing file — use faf_discover first to check. The path is confined to the project root (cwd / FAF_ALLOWED_ROOTS).

NameTypeReqDescription
goalstring––
languagestring––
namestring––
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_model ~85

Get a 100% Trophy-scored example .faf file for a specific project type. Returns a complete, realistic project.faf that fills all 21 scored slots. Use this as a reference when building or improving a .faf file — shows exactly what 100% looks like. Call without arguments to list all 15 available project types.

NameTypeReqDescription
project_typestring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_read ~55

Read project DNA from a .faf file. Returns the full parsed structure including project info, stack, preferences, and scoring data. Use this as the first step to understand any FAF-enabled project.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_score ~63

Quick Mk4 score check — returns score (0-100%), tier, and slot counts. Uses the Mk4 Championship 21-slot scoring engine for universal parity. Use this for status checks; use faf_validate when you need error details.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_stringify ~55

Convert parsed FAF data back to YAML string. Useful for displaying the raw .faf content or preparing it for editing. Reads the file, parses it, then re-serializes to clean YAML.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

faf_validate ~61

Validate a .faf file and return score, tier, and issues. Returns errors (must fix) and warnings (should fix) with specific messages. Use after faf_init or when checking if a .faf file meets quality standards.

NameTypeReqDescription
pathstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.Wolfe-Jam/gemini-faf-mcp server?

io.github.Wolfe-Jam/gemini-faf-mcp runs locally as a PyPI package, launched with uvx gemini-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.

pypi · gemini-faf-mcp

# add to Claude Code
claude mcp add wolfe-jam-gemini-faf-mcp -- uvx gemini-faf-mcp
Common questions

What is the io.github.Wolfe-Jam/gemini-faf-mcp server?

io.github.Wolfe-Jam/gemini-faf-mcp is listed in the public MCP registry as io.github.Wolfe-Jam/gemini-faf-mcp. Persistent project context for Google Gemini. Python/FastMCP. IANA-registered .faf format. This page covers its PyPI package (gemini-faf-mcp).

Is the io.github.Wolfe-Jam/gemini-faf-mcp server safe to use?

io.github.Wolfe-Jam/gemini-faf-mcp scores 89 out of 100 on VerifyMCP. We recorded 10 known advisories against it as of 4 November 2026. Its build provenance is signed and verified. 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.Wolfe-Jam/gemini-faf-mcp server expose?

io.github.Wolfe-Jam/gemini-faf-mcp exposes 12 tools: faf_read, faf_validate, faf_score, faf_discover, faf_init, and 7 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.

Is the io.github.Wolfe-Jam/gemini-faf-mcp server still maintained?

io.github.Wolfe-Jam/gemini-faf-mcp is marked deprecated in the MCP registry. We last reached this channel on 4 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.Wolfe-Jam/gemini-faf-mcp server under?

io.github.Wolfe-Jam/gemini-faf-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.