FRESH — Shared URL Freshness Intelligence

io.github.GSterlingPress由 GitHub 账号 GSterlingPress 发布v0.1.3更新于 Oct 25, 2026

Decide whether an agent should reuse cached URL knowledge or fetch the resource again.

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

概览

AI 生成的概览

一个远程 MCP 服务，用于判断此前见过的网址是否可能仍然足够新、可以复用，还是应当重新抓取。

可以做什么
在再次获取某个网址前先查询，依据共享的变更历史和容忍时间窗返回 REUSE、REFETCH 或 UNKNOWN 决策。在完成一次获取后上报新鲜度证据，例如时间戳、ETag、Last-Modified 和内容哈希，以充实共享历史。决策偏保守：证据不足时返回 UNKNOWN。
适用场景
适合会缓存或嵌入网页内容的助手，用来避免重复抓取、重新爬取、重新渲染或重新嵌入可能未变化的页面。最适合反复访问同一批网址、希望在真正发起获取前先做低成本判断的工作流。
运行要求
需要远程 streamable HTTP 端点；未声明本地软件包、账号、API 密钥或环境变量。需要能访问该托管服务的网络。查询调用需要网址、上次见到的时间和容忍秒数；上报调用需要网址、观测时间以及可选的 ETag、Last-Modified 和内容哈希。
安装前请注意
该服务自述为早期版本的实验性生产基础设施，决策可能不可靠。提交的网址会以单向哈希连同汇总观测元数据保存，托管方仍能得知哪些网址被查询。不要发送原始页面内容、Cookie、目标站点凭据或客户数据；服务称并不需要这些。

安装

在 SourceWeft 中

  1. 打开 控制台中的 FRESH — Shared URL Freshness Intelligence，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.GSterlingPress%2Ffresh/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "fresh-shared-url-freshness-intelligence": {
      "type": "http",
      "url": "https://fresh-api-production-c783.up.railway.app/mcp"
    }
  }
}

README

FRESH

Know whether to fetch again.

FRESH is shared URL freshness intelligence for AI agents. Before re-fetching, re-scraping, re-rendering, or re-embedding a URL, ask whether the previously seen version is probably still fresh enough to reuse.

Production base URL: https://fresh-api-production-c783.up.railway.app

MCP endpoint: https://fresh-api-production-c783.up.railway.app/mcp

FRESH returns one of three decisions:

  • REUSE — cached knowledge is probably still fresh enough
  • REFETCH — the URL is likely stale enough to justify another retrieval
  • UNKNOWN — evidence is insufficient; FRESH prefers uncertainty over false confidence

Why FRESH exists

A local cache knows when you last fetched something. It does not know whether the outside resource changed since then, nor what other callers recently observed. FRESH builds shared, privacy-safe URL change history from timestamps, ETags, Last-Modified values, and content hashes.

REST

POST /v1/check

json
{"url":"https://example.com/docs/api","lastSeenAt":"2026-08-13T12:00:00Z","toleranceSeconds":3600}

POST /v1/observe

json
{"url":"https://example.com/docs/api","observedAt":"2026-08-13T13:00:00Z","etag":"abc123","lastModified":"Wed, 13 Aug 2026 12:45:00 GMT","contentHash":"sha256:..."}

Raw page content is not required.

MCP

  • fresh_check — decide whether to retrieve a URL again
  • fresh_observe — report privacy-safe freshness evidence after retrieval

Privacy

FRESH does not need raw page contents, cookies, target-site credentials, or customer payloads. URL keys are stored as one-way hashes with aggregate observation metadata.

Stranger verification

A core-tool invocation is evidence of use, not automatically proof of a genuine stranger. FRESH classifies candidate activity as KNOWN_VALIDATOR, LIKELY_VALIDATOR, CONTROLLED_TEST, UNKNOWN_MACHINE, or CREDIBLE_REAL_USE. Only CREDIBLE_REAL_USE advances stranger milestones.

Our acceptance/smoke traffic uses X-Tollbooth-Internal: 1 or X-Fresh-Internal: 1 so it cannot earn stranger credit.

Production acceptance gate

Every Railway deployment now performs live internal checks against the running service before /health can return 200. The gate exercises REST, UNKNOWN, REUSE, REFETCH, persistent observation reload, MCP initialize, MCP tool discovery, MCP fresh_check, and verifies that the controlled self-test does not increase the verified-stranger count.

Status

v0.1.2 experimental production infrastructure. Priorities: conservative decisions, low latency, sub-penny economics, privacy-safe shared learning, REST + MCP, durable observations, and auditable real-use analytics.

来源：README.md，提交 12137c0

工具

2

fresh_check

Should I Fetch This URL Again?

Return REUSE, REFETCH, or UNKNOWN before retrieving a URL again.

输入参数url必填lastSeenAt必填toleranceSeconds

fresh_observe

Report URL Observation

Report privacy-safe freshness metadata from a completed retrieval.

输入参数url必填etagobservedAtcontentHashlastModified

版本历史

1
  1. v0.1.3最新Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。