MCP工具

Cloud (no install)

Add to your Claude Desktop config and restart:

Mac: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Restart Claude. Done.

Prefer a guided setup? Visit freshcontext-site.pages.dev — 3 steps, no terminal.

Deployment & infrastructure

The reference implementation runs on Cloudflare's global edge:

• D1 database — 18 watched queries running on 6-hour cron with relevancy scoring
• KV-backed rate limiting — 60 req/min per IP across all edge nodes
• Defensive valves — clock-skew rejection (5min tolerance), hard floor at R_t<5, lazy decay at read time
• Provenance — Ha-Pri v1 SHA-256 provenance stamps on stored signals; hard tamper enforcement is a future Ha-Pri v2 path
• Schema migrations — promise-gated, idempotent, run on first request after deploy

Production: https://freshcontext-mcp.gimmanuel73.workers.dev

---

Quick start

For Claude Desktop, Codex, npx, global npm, and source-checkout setup, see the concise client setup guide.

Usage examples

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.

Primary MCP interface

The clearest MCP path is evaluate_context.

It accepts candidate context from any retriever, agent, database, local script, note parser, or adapter output:

{
  "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
    }
  ]
}

FreshContext returns decision-first output:

• Decision
• Meaning
• Action
• Warnings
• Source
• Freshness
• Rank score
• Utility
• Confidence
• Why

Structured results also include a readable object for humans:

{
  "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."
    ]
  }
}

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 is part of the npm/local stdio MCP server prepared for 0.4.0. The hosted Cloudflare Worker MCP endpoint was last verified separately at 0.4.0 / 22 tools. The Worker remains a separate deployment surface, so future package interfaces should be re-verified remotely before being claimed live.

Reference adapters

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.