io.github.PrinceGabriel-lgtm由 GitHub 帳號 PrinceGabriel-lgtm 發布v0.5.3更新於 Oct 24, 2026
Context integrity for AI agents: evaluate freshness, confidence, provenance, and decision readiness.
FreshContext 評估候選脈絡的時效性、信心度與來源，並提供唯讀轉接器從公開來源擷取帶時間戳的資料。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.PrinceGabriel-lgtm%2Ffreshcontext/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"freshcontext": {
"type": "http",
"url": "https://api.freshcontext.dev/mcp"
}
}
}This package is no longer developed. 0.5.3 is the last release of
freshcontext-mcp. It and every earlier release stay available under the MIT License, as is; there will be no further feature releases. For FreshContext services, see https://freshcontext.dev. Security reports: see SECURITY.md.
I asked Claude to help me find a job. It gave me a list of openings. I applied to three of them. Two didn't exist anymore. One had been closed for two years.
Claude had no idea. It presented everything with the same confidence.
That's the problem freshcontext fixes.
This repository is the integrated FreshContext Core/MCP package.
Category: context integrity infrastructure. FreshContext sits between context acquisition and agent action. Its job is to decide whether information entering an AI workflow is still fresh, attributable and coherent enough for the system to rely on. Core is the reusable engine that scores, ranks, explains and turns candidate context into decision-ready context, with signed verdicts recorded in a verifiable ledger. MCP is the first live host interface over that engine — one interface over the methodology, not the product itself.
[npm version] [License: MIT] [MCP Registry]
Live demo: api.freshcontext.dev/demo — same model, same query, two completely different answers. Only the temporal layer changed.
Integrate it into an existing stack: freshcontext.dev/integration — start with one bounded RAG, agent, retrieval, or governance workflow and objective acceptance criteria.
Large language models retrieve web data semantically. Cosine similarity finds the documents that match a query best — but cosine doesn't know when a document was written.
So a 2022 blog post and a 2026 paper can score nearly identically. The model gets a context window full of stale documents and faithfully summarizes 2022 advice for a 2026 question.
That's not hallucination. That's correct summarization of corrupted retrieval.
Most RAG pipelines rank context correctly semantically but incorrectly temporally.
FreshContext is context integrity infrastructure for AI agents and retrieval systems. It sits between retrieval and reasoning:
FreshContext evaluates freshness, source profile, confidence, utility, provenance material, and failure honesty before context reaches the LLM. The temporal core uses Decay-Adjusted Relevancy:
R_0 — base semantic relevancy (whatever your retriever already gives you)λ — source-specific decay constant (HN ≈14h half-life, blogs ≈29d, academic papers ≈1.6y)t — hours elapsed since publicationR_t — decay-adjusted relevancy at query timeThat's the core correction. No model swap. No re-embedding. No re-indexing. The layer drops onto whatever retrieval pipeline you already have.
The layer is the product. The named adapters shipped with this repo demonstrate compatibility across different source classes. The DAR engine, the freshness envelope, Source Profiles, and the FreshContext Specification are the moat.
Every FreshContext-compatible response wraps content in a structured envelope:
When it was retrieved. Where it came from. How confident we are the date is accurate.
The FreshContext Specification v1.2 is published as an open standard under MIT licence. Any tool, agent, or system that wraps retrieved data in this envelope is FreshContext-compatible. → Read the spec · Read the methodology
FreshContext Core is the reusable center of the current integrated package. It owns signal normalization, freshness scoring, Source Profiles, decision output, envelope formatting, failure guards, shared types, rank/explain primitives, and the context-conditioned utility primitive.
MCP is the primary reference/interface implementation over Core. Claude Desktop is supported, but not required. The MCP tool surface exposes named reference adapters and a live interface for using the system.
The production Cloudflare Worker now uses Core-backed envelope generation. Worker-specific concerns remain outside Core: MCP transport, runtime guards, KV cache policy, cache metadata injection, JSON parse/replace cache helpers, D1 feeds, cron, rate limiting, and Store/feed scoring/provenance.
See Architecture for the layer boundaries, the package surface, and what is not yet separated.
FreshContext Core is also available directly from the current MCP package:
This is a Core subpath export inside freshcontext-mcp, not a standalone freshcontext-core package yet. The root package and freshcontext-mcp binary remain the MCP reference host.
The clearest MCP path is evaluate_context.
It accepts candidate context from any retriever, agent, database, local script, note parser, or adapter output:
FreshContext returns decision-first output:
Structured results also include a readable object for humans:
The readable object translates Core decisions into user-facing language. It does not change ranking, decision labels, utility scoring, or source intake. Utility helps explain usefulness for the current question; it remains explanatory and does not control default decision labels or ranking.
FreshContext does not certify truth. It records why context was used, supported, questioned, refreshed, watched, or excluded before it reaches a model.
evaluate_context does not fetch URLs, crawl, scrape, browse, read folders, or call adapters. It only evaluates candidate context the caller provides.
Current boundary: evaluate_context ships in the npm/local stdio MCP server. The hosted Cloudflare Worker MCP endpoint is a separate deployment surface and is verified independently — check /v1/health for its live version and tool count rather than assuming parity with the package. The Worker remains a separate deployment surface, so future package interfaces should be re-verified remotely before being claimed live.
FreshContext's primary evaluate_context path does not fetch, crawl, scrape, browse, read folders, or call adapters. The MCP package also includes read-only reference adapters that use network access only when those adapter tools are invoked. Supply-chain scanners may therefore report package network access; that applies to the optional adapter surface, not to caller-provided context evaluation.
Beyond the per-call Core/MCP paths, the production Worker deployment exposes a continuous, decay-scored, deduplicated feed. This is an advanced deployment surface, not the required way to use FreshContext Core:
Every signal is stamped with base_score, rt_score, entropy_level (low / stable / high), ha_pri_sig (Ha-Pri v1 SHA-256 provenance reference), semantic_fingerprint (cross-adapter dedup), and published_at. Ready for direct LLM or agent consumption — no synthesis required.
Production endpoint: https://api.freshcontext.dev
The repo ships named reference adapters that demonstrate how different source classes can become FreshContext-compatible. Each adapter keeps its own name because it represents a source boundary; the adapter count is operational proof, not the product headline.
For Claude Desktop, Codex, npx, global npm, and source-checkout setup, see the concise client setup guide.
Add to your Claude Desktop config and restart:
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude. Done.
Prefer a guided setup? Visit freshcontext.dev — 3 steps, no terminal.
Requires: Node.js 20+ (nodejs.org)
Add to Claude Desktop config:
Mac:
Windows:
"command not found: node" — Use the full path:
Config file doesn't exist:
The npm run demo:* commands below are source-checkout workflows for contributors and evaluators using a cloned repository. The published npm package is the MCP server/runtime package and does not include repo-only source examples or tests.
From an installed npm package, the supported runtime entrypoints are npm start and the freshcontext-mcp binary. Repo-only scripts such as tests, demos, smoke checks, and trust scans print a source-checkout notice when their source files are not present.
The Apify Actor entrypoint remains available in the source checkout for separate actor packaging, but it is intentionally not part of the published MCP npm runtime package.
Run the local release gate before a release, package review, demo, or PR review:
The gate runs the Trust Scanner with repo-map reporting, npm package-boundary inspection, deterministic claim checks, and --fail-on fail. It is local-only, does not publish or deploy, does not send telemetry, and does not replace dedicated security scanners.
Generate review reports when you need a shareable summary:
To write a Markdown report file explicitly:
FreshContext can evaluate candidate context you provide as a local JSON file:
To pass a different file:
Included examples:
Minimal shape:
This local demo does not fetch URLs, crawl, or read folders. It evaluates candidate context you provide and returns decision-first output: Decision, Meaning, Action, Warnings, and supporting metrics.
In an MCP client, use evaluate_context when you already have candidate context from another retriever, database, agent, or script:
Use the named reference adapters when you want FreshContext's current MCP package to fetch public source examples for you.
Should I build this idea?
Returns funding signal, pain signal, crowding signal, market signal, ecosystem signal, and launch signal — all timestamped.
Full company intelligence in one call:
SEC filings + federal contracts + global news + changelog + market data.
Did that company just disclose something material?
8-K filings are legally mandated within 4 business days of any material event — CEO change, acquisition, breach, major contract.
Is this dependency still actively maintained?
Returns the last 8 releases with exact dates. If the last release was 18 months ago, you'll know before you pin the version.
The reference implementation runs on Cloudflare's global edge:
Production: https://api.freshcontext.dev
The engine is deliberately separable from the interface it is reached through. The same Core runs in each of these without a rewrite:
Only the MCP and standalone modes are exercised in production today. The others are integration seams the architecture already supports, not shipped configurations.
Split three ways so that genuine engineering risk is never filed as optionality. Nothing outside Production core is a live product claim.
/v1/verify endpoint — ledger-backed verdict verification, answering for both the legacy HMAC path and Ed25519, and reporting which was used via verification_methodevaluate_context tool for caller-provided candidate context/demoworkflow_dispatch only, OIDC-backed, provenance-enabled, and gated by version/verification checks. One explicit run publishes npm first, verifies it, then publishes the matching manifest to the official MCP Registry with GitHub OIDCFRESHCONTEXT_HA_PRI_V4 with Ed25519. A third party can verify a verdict
with no FreshContext account, no API key and no call to FreshContext — using the key
document the Worker publishes at /.well-known/freshcontext-signing-keys.json and either
verifier shipped in the npm tarball: scripts/verify-offline.mjs (Node, standard library)
or scripts/verify_offline.py (Python, no dependencies at all). Written up for the
sceptic rather than the maintainer in VERIFYING.md.fc-2026-09-ceced1ab published and active. Keys are append-only, so a
rotation never invalidates a verdict signed under a key that has since been retired.attestation-proof.yml — obtains a live verdict, verifies it with both shipped
verifiers, runs tampered-payload and tampered-signature negative controls, and confirms
the stored ledger row is V4 rather than only the emitted response block. On demand and
daily; every input it uses is public, so it needs no credentials to run.In flight on the core, not an expansion surface:
These are integration seams the architecture supports and the engine does not yet implement. Stated in future tense on purpose.
evaluate_context emits decisions and warnings; the enforcement state machine does not exist — quarantine and block are not implemented anywhere in the codebase.extract_gdelt — tone scores, goldstein scale, event codesFuture work is organized in FreshContext Future Lanes. Roadmap items are not live product claims until implemented and validated.
PRs welcome. The highest-value contributions improve the caller-provided context path, decision output, host integrations, and FreshContext-compatible signal quality. New reference adapters are useful when they preserve source boundaries and emit timestamped, failure-honest context — see src/adapters/ for examples and FRESHCONTEXT_SPEC.md for the compatibility contract.
If you're building something FreshContext-compatible, open an issue and we'll add you to the ecosystem list.
MIT
Built by Immanuel Gabriel — Namibia 🇳🇦 "The work isn't gone. It's just waiting to be continued."
Also on: MCP Registry · npm
來源：README.md，提交 53ed204
Evaluate caller-provided candidate context and return decision-ready output. This is the primary FreshContext judgment path: it does not fetch, crawl, scrape, browse, read folders, or call adapters.
nowintent必填profile必填signals必填Extract real-time data from a GitHub repository — README, stars, forks, last commit, topics. Returns timestamped freshcontext.
url必填Extract top stories or search results from Hacker News. The url field accepts an HN/Algolia URL or a plain search query.
url必填Extract research results (title, authors, year, snippet) from a Google Scholar search URL. Scholar exposes only the publication year, not an exact date, so freshness confidence is capped at medium.
url必填Withdrawn in 0.5.3 pending review of source terms. Returns an error; kept so existing clients get a clear answer.
url必填Search GitHub for repositories matching a keyword. Returns top results by stars.
query必填npm and PyPI package metadata — version history, release cadence, last updated.
packages必填Extract recent posts from a subreddit (e.g. 'r/MachineLearning') or a Reddit search/listing URL. Returns title, subreddit, author, score, comment count, and post date per result.
url必填Extract recent Product Hunt launches by keyword/topic search or a PH URL. Returns name, tagline, votes, comment count, topics, and launch date per result.
url必填No-key stock quote data via Stooq. Accepts comma-separated ticker symbols and returns quote/OHLC/volume observations with timestamps.
url必填Search for real-time job listings with freshness badges on every result. Sources: Remotive + HN Who is Hiring.
query必填max_lengthComposite tool. Queries GitHub + HN + npm simultaneously. Returns a unified landscape report with each source's own freshness.
topic必填Search arXiv for research papers via the official API. Pass a topic or full arXiv API URL. Returns titles, authors, dates, abstracts.
url必填Update history for any product. Accepts a GitHub repo URL or an npm package name. Returns version numbers, release dates, and entries.
url必填Global news intelligence from GDELT. Monitors news from every country in 100+ languages, updated every 15 minutes. Returns articles with source country, language, date.
url必填Singapore Government procurement opportunities (GeBIZ via data.gov.sg). Search by keyword, agency name, or empty for all recent tenders.
url必填US federal contract awards from USASpending.gov. Search by company name (e.g. 'Palantir'), keyword, or NAICS code. Returns amounts, dates, agencies.
url必填SEC 8-K filings via EDGAR full-text search. 8-K = legally mandated material event disclosures (CEO changes, M&A, breaches). Pass company name, ticker, or keyword.
url必填Composite government intelligence: federal contract awards (USASpending) + dev community awareness (HN) + GitHub repo activity + product release velocity (changelog). 4-source unified report.
query必填github_urlComposite financial intelligence: Stooq quote data + HN sentiment + Reddit discussion + GitHub ecosystem + product changelog. 5-source unified report.
tickers必填company_namegithub_queryMost complete single-call company intelligence: SEC 8-K filings + USASpending federal contracts + GDELT global news + product changelog + Stooq quote data. 5 unique sources.
tickercompany必填github_urlIdea validation composite: HN pain signals + YC funded competitors + GitHub crowding + jobs market signal + npm/PyPI ecosystem + Product Hunt launches. 6 sources.
idea必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
candidate context -> FreshContext Core -> decision-ready context -> model / agent / appR_t = R_0 · e^(−λt)[FRESHCONTEXT]Source: https://github.com/owner/repoPublished: 2024-11-03Retrieved: 2026-03-05T09:19:00ZConfidence: high---... content ...[/FRESHCONTEXT]import { evaluateSignals, interpretEvaluations, getSourceProfile, normalizeSignal, calculateHaPriV2,} from "freshcontext-mcp/core";{ "profile": "academic_research", "intent": "citation_check", "signals": [ { "title": "Example source", "content": "Candidate context text...", "source": "https://example.com/source", "source_type": "arxiv", "published_at": "2026-05-24T12:00:00.000Z", "retrieved_at": "2026-05-24T13:00:00.000Z", "semantic_score": 0.92 } ]}{ "decision": "cite_as_primary", "label": "Cite as primary", "readable": { "label": "Primary source", "summary": "This source is strong enough to use as main evidence.", "why": [ "Strong semantic match and current freshness for arxiv.", "source profile academic_research uses lenient date policy", "intent profile citation_check selected" ], "action": "Use this as main evidence while preserving citation and provenance.", "warnings": [ "FreshContext judges citation readiness and context usefulness; it does not certify truth." ] }}GET /v1/intel/feed/:profile_id?limit=20&min_rt=0{ "mcpServers": { "freshcontext": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.freshcontext.dev/mcp"] } }}git clone https://github.com/PrinceGabriel-lgtm/freshcontext-mcpcd freshcontext-mcpnpm installnpx playwright install chromiumnpm run build{ "mcpServers": { "freshcontext": { "command": "node", "args": ["/Users/YOUR_USERNAME/path/to/freshcontext-mcp/dist/server.js"] } }}{ "mcpServers": { "freshcontext": { "command": "node", "args": ["C:\\Users\\YOUR_USERNAME\\path\\to\\freshcontext-mcp\\dist\\server.js"] } }}which node # copy this output, replace "node" in configmkdir -p ~/Library/Application\ Support/Claudetouch ~/Library/Application\ Support/Claude/claude_desktop_config.jsonnpm run trust:gatenpm run trust:reportnpm run trust:report:jsonnpm run trust:report -- --output TRUST_SCAN_REPORT.mdnpm run demo:evaluate:filenpm run demo:evaluate:file -- path/to/sources.jsonnpm run demo:evaluate:file -- examples/sources.academic.example.jsonnpm run demo:evaluate:file -- examples/sources.jobs.example.json{ "profile": "academic_research", "intent": "citation_check", "signals": [ { "title": "...", "content": "...", "source": "...", "source_type": "arxiv", "published_at": "...", "retrieved_at": "...", "semantic_score": 0.92 } ]}Use evaluate_context with profile "academic_research", intent "citation_check", and these candidate signals: [...]Use extract_idea_landscape with idea "procurement intelligence saas"Use extract_company_landscape with company "Palantir" and ticker "PLTR"Use extract_sec_filings with url "Palantir Technologies"Use extract_changelog with url "https://github.com/org/repo"