FreshContext HQ

FreshContext is temporal intelligence infrastructure for AI systems.

Rank live signals by freshness, provenance, and temporal relevance before they reach an agent, feed, or retrieval workflow.

Use FreshContext through MCP, APIs, feeds, and freshness-aware infrastructure tools.

v0.3.17 21 tools live MCP + APIs + feeds
21freshness-aware MCP tools
3live product API surfaces
DARdecay-aware ranking model
JSONstructured provenance envelope

The scoring layer sits before the agent.

FreshContext gives agents a temporal view of retrieved information: where it came from, when it was published, when it was retrieved, and how quickly it should lose ranking weight.

Envelope Text + JSON
[FRESHCONTEXT]
Source: https://example.com/source
Published: 2026-05-12T09:00:00Z
Retrieved: 2026-05-12T10:00:00Z
Confidence: high
Score: 95/100 (current)
---
Fresh, source-grounded content...
[/FRESHCONTEXT]

[FRESHCONTEXT_JSON]
{ "freshcontext": { "freshness_score": 95 } }
[/FRESHCONTEXT_JSON]

One temporal primitive, multiple product surfaces.

The current ecosystem spans a core MCP server, two vertical signal feeds, and an operations intelligence system for the Cloudflare infrastructure behind them.

Core Live

FreshContext Core

Temporal scoring and MCP infrastructure for agent retrieval workflows.

Feed API live

Fresh HN Feed

Freshness-ranked Hacker News intelligence for tracking live technical signals.

Feed API live

Fresh Jobs Feed

Freshness-ranked jobs intelligence with AI/ML as the default category.

Ops GitHub live

FreshContext Ops Pulse

Plain-English Cloudflare operations diagnosis for Workers, D1, cron systems, logs, and runtime analysis.

Agents should not treat stale context and live context as equal.

FreshContext helps retrieval workflows preserve time as a first-class signal. It does not claim to solve hallucinations; it helps agents avoid stale context and rank live information more correctly.

Decay-aware ranking R(t) = R0 · e-λt

Older information loses ranking weight unless reinforced by newer signals. Different sources decay at different speeds because a market quote, job listing, release note, repository, and paper do not age the same way.

Provenance is preserved.Responses keep the source URL, adapter, confidence, and retrieval timestamp visible to the agent.
Source time stays separate.The content date is not mixed into prose; it is carried as structured metadata.
Envelopes are machine-readable.Agents can use the JSON block instead of guessing freshness from human-readable text.
Caches remain honest.Cached responses can still communicate when the content was retrieved and how freshness should be interpreted.

Use FreshContext through Claude Desktop, MCP, or live HTTP APIs.

The hosted Worker endpoint is the fastest setup. The npm package is available for local stdio transport when you want the server on your machine.

1

Open Claude Desktop config

Claude Desktop → Settings → Developer → Edit Config.

2

Add the remote MCP endpoint

This uses the deployed FreshContext Worker. No local Node install required.

{
  "mcpServers": {
    "freshcontext": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://freshcontext-mcp.gimmanuel73.workers.dev/mcp"
      ]
    }
  }
}
3

Restart Claude Desktop

All 21 tools appear automatically after Claude reconnects to the MCP server.

1

Install from npm

npm install -g freshcontext-mcp
2

Add local stdio server

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or your Claude config path on Linux.

{
  "mcpServers": {
    "freshcontext": {
      "command": "freshcontext-mcp"
    }
  }
}
1

Install from npm

npm install -g freshcontext-mcp
2

Find the executable path

where freshcontext-mcp
3

Add it to Claude Desktop

Use the path returned by where freshcontext-mcp in %APPDATA%\Claude\claude_desktop_config.json.

{
  "mcpServers": {
    "freshcontext": {
      "command": "C:\\Users\\YOUR_NAME\\AppData\\Roaming\\npm\\freshcontext-mcp.cmd"
    }
  }
}

Prompts that return freshness-aware context.

These examples route through MCP tools and return provenance, content dates, confidence, freshness_score, and structured JSON.

Use extract_hackernews to find recent discussion around browser agents.
Use extract_company_landscape for Palantir with ticker PLTR.
Use search_jobs to find current AI engineer roles in Europe.
Use extract_idea_landscape for "AI operations monitoring".

Vertical feeds expose FreshContext as simple HTTP surfaces.

The feeds are intentionally narrow and inspectable: useful for dashboards, scheduled agents, Apify actors, and direct API calls.

Fresh HN Feed

API
curl "https://fresh-hn-feed.gimmanuel73.workers.dev/v1/hn/feed?limit=10"

Fresh Jobs Feed

API
curl "https://fresh-jobs-feed.gimmanuel73.workers.dev/v1/jobs/feed?category=ai&limit=10"

MCP Health

Endpoint
curl "https://freshcontext-mcp.gimmanuel73.workers.dev/health"

FreshContext feed actors are live on Apify.

Apify Actor Apify live

Fresh HN Feed Actor

Freshness-ranked Hacker News feed actor for scheduled runs, datasets, and workflow automation.

Apify Actor Apify live

Fresh Jobs Feed Actor

Freshness-ranked jobs feed actor for AI/ML role monitoring and marketplace workflows.

Measured extensions to the same temporal ranking primitive.

Trend Half-Life API

Expose source-specific decay estimates for downstream retrieval systems.

Research Resurgence Tracker

Detect papers and topics becoming newly relevant again.

Signal Digest Agent

Push compact digests when important signals cross freshness thresholds.

GitHub Release Intelligence Feed

Rank release notes by recency, velocity, and operational relevance.