FreshContext v0.3.18

FreshContext decides what context deserves to reach the model.

A context gateway for agents and apps: raw retrieval results become freshness-ranked, explained, decision-ready context.

npm latest 0.3.18 21 MCP tools local REST handler source profiles
raw fresh arXiv paper with clear date cite first
rank older source, still useful foundation supporting
warn missing publication date verify
guard blocked/error response exclude

Raw signals in. Decision-ready context out.

FreshContext sits between retrieval and reasoning. It does not replace the model; it decides what retrieved context should be trusted, cited, refreshed, verified, backgrounded, or ignored before the model sees it.

1

Context Gateway

Accept candidate context from MCP tools, local files, app code, or future adapters.

2

Core Evaluation

Normalize signals, score freshness, preserve confidence, and explain uncertainty.

3

Source Profiles

Apply source-aware aging policy for docs, code, research, finance, jobs, social, and local context.

4

Decision Layer

Return useful actions: use first, cite, refresh, verify, watch, background, or exclude.

New user start here

Install it, then ask better context questions.

Use the npm package with an MCP client, then open the demo runbook to see how FreshContext explains source quality.

Builder / buyer integrate

Put FreshContext before your model.

Use the public MCP surface now, inspect the Core API docs, and track the REST/SDK/Operator surfaces as they mature.

Investor / partner proof

Look for the standard layer.

The asset is a repeatable context judgment layer: standard inputs, source profiles, decisions, audit trails, and host interfaces.

The release is small, real, and installable.

FreshContext 0.3.18 is a public MCP package with a working local context pipeline, adapter metadata, a first arXiv signal path, deterministic demos, and release integrity checks.

Surface Status What it proves
MCP package live 21 read-only tools can run through the published `freshcontext-mcp` package.
Bring-your-own-context local A user can pass JSON signals and get decision-first output locally.
arXiv signal proof additive One adapter path now reaches Core evaluation and decisions without changing MCP behavior.
Operator / retrieve roadmap Retrieval orchestration, crawling, browser search, and file search are intentionally not claimed as live.
Boundary honest scope

Not another vague agent.

FreshContext is the evidence layer an agent, app, researcher, or workflow can use before reasoning. MCP is one interface; Core is the reusable judgment layer.

Use what is live. See what is next.

FreshContext is host-agnostic by design. MCP is live today; local demos and docs prove the Core pipeline; REST, SDK, CLI, and Operator mode are staged deliberately instead of overclaimed.

MCP live

Agent interface

Install `freshcontext-mcp` and expose 21 read-only tools through MCP stdio clients.

Core local

Evaluation engine

Core owns evaluation, source profiles, ranking, explanations, and decision meaning.

REST local primitive

HTTP host shape

A local Fetch-style handler exists as a host primitive. A public REST product is still roadmap.

SDK / CLI / Operator coming soon

Workflow layer

Future surfaces will make retrieval orchestration and local workflows easier without blurring what is live today.

Use the published MCP package today.

The cleanest public path is local MCP through npm. Demos and source-checkout workflows live in the GitHub repo; the installed package supports the MCP server entrypoint.

Install globally

Use this when configuring Claude Desktop or another MCP stdio client.

npm install -g freshcontext-mcp
freshcontext-mcp

Try the source demos

Clone the repo for bring-your-own-context demos, arXiv signal proof, Trust Scanner, and release integrity checks.

The local REST handler, Operator mode, retrieval orchestration, browser crawling, dashboards, billing, and webhooks are not presented here as deployed product surfaces.

Show the decision layer, not a pile of links.

For a live talk, lead with the context-integrity demo, then show npm install, then show the runbook. Keep future surfaces framed as roadmap.

Demo static

Context integrity demo

Shows fresh, stale, unknown-date, and failed context before and after FreshContext evaluation.

Docs runbook

Operational demo runbook

A practical talk track for showing FreshContext without overclaiming future Operator or platform work.

Contact founder

Talk, demo, or integration

Use the contact page for outreach. A dedicated FreshContext email is planned.