updated 2026-09-26 06:32 UTC

Persistent Project Context for xAI Grok

Wolfe-Jam/grok-faf-mcp

Persistent Project Context for xAI Grok — IANA-registered .faf format · MCP server on a URL

MCP Servers TypeScript Listed MIT

Is Persistent Project Context for xAI Grok safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.9 / 10
Provenance None
Signed commits 39%
Last push 3d ago
Compare Persistent Project Context for xAI Grok

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Persistent Project Context for xAI Grok scores 61.7/100 (Grade C), ranked #583 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.9/10; 39% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Persistent Project Context for xAI Grok compares in MCP Servers

  1. #330 MCP Cn Commerce 61.8 +0.1
  2. #331 Arxiv MCP Server 61.8 +0.1
  3. #332 Persistent Project Context for xAI Grok 61.7 this agent
  4. #333 Unreal Engine API Documentation 61.6 −0.1
  5. #334 Web Researcher MCP 61.5 −0.2

Bars show each HVTrust score; the tick marks Persistent Project Context for xAI Grok’s 61.7.

Where the 61.7 comes from

HVTrust dimensions vs the MCP Servers average

61.7 / 100 · 100.0% confidence

Persistent Project Context for xAI Grok MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.3 / 25
1.0 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
1.3 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.2 / 20
4.1 above avg 12.1
AdoptionLog-scaled stars · package downloads
6.2 / 20
1.0 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-24
Rank Moved
Rank dropped 11 spots (#562 → #573)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Persistent Project Context for xAI Grok View MCP Servers Report missing data
48.5
Activity sub-score · out of 100
#332
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
19
Forks
2
Last Push
2026-09-23
3 days ago
Commits (4 wk)
12
Downloads (7d)
213
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼5
was #578

Analysis

Activity Inputs

48.5 / 100
StarsRepository reach
7.8 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
2.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.9 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
39%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 4
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Common questions about Persistent Project Context for xAI Grok

Persistent Project Context for xAI Grok has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Persistent Project Context for xAI Grok publish package provenance?
No published build provenance is currently detected for Persistent Project Context for xAI Grok. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Persistent Project Context for xAI Grok have an OpenSSF Scorecard?
Persistent Project Context for xAI Grok has an OpenSSF Scorecard score of 5.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Persistent Project Context for xAI Grok actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Persistent Project Context for xAI Grok use?
Persistent Project Context for xAI Grok ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Persistent Project Context for xAI Grok's commits signed?
39% of the last 100 commits to Persistent Project Context for xAI Grok are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Persistent Project Context for xAI Grok appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Persistent Project Context for xAI Grok's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Persistent Project Context for xAI Grok?

For maintainers

HVTrust scores Persistent Project Context for xAI Grok from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 24HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-09-24
Rank Moved
Rank dropped 11 spots (#562 → #573)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 272 spots (#834 → #562)
2026-09-23
HVTrust Changed
HVTrust up 34.0pts (28.2 → 62.2)
2026-09-22
Newly Listed
First tracked at rank #834
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-15
Rank Moved
Rank rose 10 spots (#574 → #564)
2026-09-14
Rank Moved
Rank rose 12 spots (#586 → #574)
2026-09-11
Rank Moved
Rank dropped 19 spots (#561 → #580)
2026-09-10
Grade Changed
Trust grade D → C
2026-09-10
Rank Moved
Rank rose 570 spots (#1131 → #561)
2026-09-10
HVTrust Changed
HVTrust up 20.0pts (41.0 → 61.0)
2026-09-09
Rank Moved
Rank dropped 18 spots (#1113 → #1131)
2026-09-07
Rank Moved
Rank dropped 19 spots (#1087 → #1106)
2026-09-06
Scorecard Added
OSSF Scorecard: 5.8/10
2026-09-06
Rank Moved
Rank rose 209 spots (#1296 → #1087)
2026-09-06
HVTrust Changed
HVTrust up 19.1pts (22.1 → 41.2)
2026-09-05
Rank Moved
Rank dropped 10 spots (#1286 → #1296)
2026-09-03
Rank Moved
Rank dropped 23 spots (#1254 → #1277)
2026-09-02
Rank Moved
Rank dropped 29 spots (#1225 → #1254)
2026-09-01
Rank Moved
Rank dropped 22 spots (#1203 → #1225)
2026-08-31
Rank Moved
Rank dropped 28 spots (#1175 → #1203)
2026-08-30
Rank Moved
Rank dropped 31 spots (#1144 → #1175)
2026-08-29
Rank Moved
Rank dropped 31 spots (#1113 → #1144)
2026-08-28
Rank Moved
Rank dropped 31 spots (#1082 → #1113)
2026-08-27
Rank Moved
Rank dropped 24 spots (#1058 → #1082)
2026-08-26
Rank Moved
Rank dropped 80 spots (#978 → #1058)
2026-08-22
Rank Moved
Rank rose 12 spots (#986 → #974)
2026-08-16
Rank Moved
Rank dropped 29 spots (#970 → #999)
2026-08-15
Rank Moved
Rank rose 11 spots (#981 → #970)
2026-08-12
Rank Moved
Rank rose 17 spots (#988 → #971)
2026-08-10
Rank Moved
Rank dropped 54 spots (#930 → #984)
2026-08-08
Newly Listed
First tracked at rank #914
GitHub → npm: grok-faf-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 61.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/persistent-project-context-for-xai-grok.svg)](https://hvtracker.net/agents/persistent-project-context-for-xai-grok)
HTML:
<a href="https://hvtracker.net/agents/persistent-project-context-for-xai-grok"><img src="https://hvtracker.net/badge/persistent-project-context-for-xai-grok.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON