Context Gateway
Accept candidate context from MCP tools, app code, local demos, or future adapters.
Context integrity before reasoning
Context that earns its place.
FreshContext decides what context deserves to reach the model. Raw retrieval results become freshness-ranked, explained, decision-ready context for agents and apps.
context gateway
Core evaluation active
source profiles
decision layer
Decision pass
raw signals -> model-ready context
raw
fresh arXiv paper with clear date
cite primary
rank
older source, still useful foundation
supporting
warn
missing publication date
verify
guard
blocked/error response
exclude
What it does
The context gateway before reasoning.
FreshContext sits between retrieval and reasoning. It does not replace the model; it turns candidate context into decisions about what should be used, cited, refreshed, verified, backgrounded, watched, or excluded.
Core Evaluation
Normalize signals, score freshness, preserve confidence, and explain uncertainty.
Source Profiles
Apply source-aware aging policy for docs, code, research, finance, jobs, social, and local context.
Decision Layer
Return useful actions: use first, cite, refresh, verify, watch, background, or exclude.
Use it now
Run the published package when you need an MCP interface.
FreshContext is the context judgment layer. The current public npm package is the easiest way to run that layer through an MCP stdio client.
Install globally
Use this when configuring Claude Desktop, Codex, 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.
Interfaces
Live today. Staged honestly.
This section is where implementation surfaces belong. FreshContext itself is the judgment layer; MCP/npm are current ways to run it, while broader hosted and orchestration surfaces remain roadmap.
MCP
live
Agent interface
Install `freshcontext-mcp` and expose named read-only reference adapters through MCP stdio clients.
Core proof
local
Evaluation and decisions
Source Profiles, BYOC JSON demos, and the arXiv signal path prove adapter output can reach Core decisions.
Roadmap
planned
REST, SDK, CLI, Operator
A local REST handler exists in source. Public REST, retrieval orchestration, crawling, dashboards, billing, and webhooks are not live product claims.
Screen-share path
Show the decision layer, not a pile of links.
For a live talk, each scroll has one job: explain the judgment layer, show the current npm/MCP path, separate live surfaces from roadmap, then offer contact.
Demo
static
Context integrity demo
Shows fresh, stale, unknown-date, and failed context before and after FreshContext evaluation.
Docs
source
Source proof
Use the public repo for implementation evidence, release notes, Core docs, and source-profile boundaries. Private demo material stays private.
Contact
founder
Talk, demo, or integration
Use the contact page for outreach. A dedicated FreshContext email is planned.