updated 2026-09-04 23:12 UTC

fastctx

yc-duan/fastctx

Fast, context-efficient repository tools for AI agents (MCP)

MCP Servers Rust Grade C Listed Apache-2.0
54.7/100
Rank #631 of 1320
Compare fastctx

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +10

Is fastctx safe? fastctx scores 54.7/100 (Grade C), ranked #631 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; recent commits are unsigned; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#306 Discord MCP — 54.8 (C) → #307 Perplexity MCP Server — 54.7 (C) → #309 MCP Cn Commerce — 54.6 (C) → #310 Funplay Unity MCP — 54.6 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 11 spots (#620 → #631)
2026-09-03
Rank Moved
Rank dropped 39 spots (#581 → #620)
2026-09-02
Rank Moved
Rank dropped 28 spots (#553 → #581)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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 fastctx View MCP Servers Report missing data
71.0
Activity sub-score · out of 100
#308
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 23:12 UTC · Repo last pushed today

Rank Trend

2026-08-26 2026-09-04

Activity & Reach

Stars
1.3k
Forks
51
Last Push
2026-09-04
today
Commits (4 wk)
34
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
17
Rank Change
▼11
was #620

Analysis

HVTrust Dimensions vs MCP Servers

54.7 / 100 · 100.0% confidence

fastctx MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
5.0 below avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
18.2 / 20
6.0 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.5 / 20
1.2 above avg 6.3

Activity Inputs

71.0 / 100
StarsRepository reach
18.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
19.3 / 25
CommunityFork signal
8.0 / 20

Supply Chain Trust

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

Is fastctx safe?

Public trust evidence for fastctx is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does fastctx publish package provenance?
No published build provenance is currently detected for fastctx. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does fastctx have an OpenSSF Scorecard?
fastctx has an OpenSSF Scorecard score of 3.7/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 fastctx actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does fastctx use?
fastctx ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are fastctx's commits signed?
0% of the last 100 commits to fastctx 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
medium confidence
Implemented
fastctx appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain fastctx?

For maintainers

HVTrust scores fastctx 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 9Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 11 spots (#620 → #631)
2026-09-03
Rank Moved
Rank dropped 39 spots (#581 → #620)
2026-09-02
Rank Moved
Rank dropped 28 spots (#553 → #581)
2026-09-01
Scorecard Added
OSSF Scorecard: 3.7/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 584 spots (#1137 → #553)
2026-09-01
HVTrust Changed
HVTrust up 29.7pts (24.9 → 54.6)
2026-08-31
Rank Moved
Rank dropped 31 spots (#1106 → #1137)
2026-08-30
Rank Moved
Rank dropped 46 spots (#1060 → #1106)
2026-08-29
Rank Moved
Rank dropped 47 spots (#1013 → #1060)
2026-08-28
Rank Moved
Rank dropped 37 spots (#976 → #1013)
2026-08-27
Rank Moved
Rank dropped 25 spots (#951 → #976)
2026-08-26
Newly Listed
First tracked at rank #951
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/fastctx.svg)](https://hvtracker.net/agents/fastctx)
HTML:
<a href="https://hvtracker.net/agents/fastctx"><img src="https://hvtracker.net/badge/fastctx.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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