Skip to main content
Glama

FRESH — Shared URL Freshness Intelligence

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
GSterlingPress/fresh-api
GitHub Stars
0
Server Listing
FRESH
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: one is for pre-retrieval status checking, the other for post-retrieval metadata observation. No overlap or ambiguity exists between them.

Naming Consistency5/5

Both tools follow the same 'fresh_' prefix with a descriptive verb ('check' and 'observe'), creating a consistent and predictable naming pattern.

Tool Count3/5

With only two tools, the set is on the thin side but appropriately scoped for a very focused freshness utility. It does not feel excessively sparse, though it is minimal.

Completeness4/5

The tool pair covers the full lifecycle of freshness handling: check before retrieval and observe after retrieval. No obvious dead ends or missing operations within this narrow domain.

Available Tools

2 tools
fresh_checkShould I Fetch This URL Again?A
Read-onlyIdempotent
Inspect

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

Inputs: url (required), lastSeenAt (required), toleranceSeconds.

fresh_observeReport URL ObservationBInspect

Report privacy-safe freshness metadata from a completed retrieval.

Inputs: url (required), etag, observedAt, contentHash, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A shared distillation cache for AI agents — clean-crawl a URL once, distill it to token-optimal markdown, and serve it content-addressed across every agent (~73–89% fewer tokens). Includes a collective-notes layer and cutoff-aware change detection.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Analyzes, generates, simulates, and optimizes caching strategies across HTTP, CDN, and browser layers for AI agents.
      40 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check and contribute recent observations of source-backed facts, reducing redundant revalidation of unchanged information.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.