Skip to content

FRESH — Shared URL Freshness Intelligence MCP server

io.github.GSterlingPress/freshGSterlingPressstreamable-httpv0.1.3Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FRESH — Shared URL Freshness Intelligence MCP server can do

The FRESH — Shared URL Freshness Intelligence MCP server is published by the GitHub account GSterlingPress. It has 2 tools. It can create or change data (1 tool: fresh_observe), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (fresh_check and fresh_observe); 2 tools can send data out of your system (fresh_check and fresh_observe).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • fresh_observeReport privacy-safe freshness metadata from a completed retrieval.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Report privacy-safe freshness metadata from a completed retrieval.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • fresh_checkReturn REUSE, REFETCH, or UNKNOWN before retrieving a URL again.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Return REUSE, REFETCH, or UNKNOWN before retrieving a URL again.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://fresh-api-production-c783.up.railway.app/mcp: tools/list returned 2 tools to an anonymous client, including fresh_observe (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http fresh https://fresh-api-production-c783.up.railway.app/mcp
claude mcp add --transport http fresh https://fresh-api-production-c783.up.railway.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__fresh__fresh_check",
      "mcp__fresh__fresh_observe"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fresh. Review it before you use it.

Capability tags behind 2 rules
  • mcp__fresh__fresh_check untrusted-input, outbound
  • mcp__fresh__fresh_observe untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.GSterlingPress/fresh/verify?hash=68909d0a5d34c20f39beb53e930c55a2332df5abffb68005365c4c396dcca6c3" | jq -e '.changed == false'

Pinned hash 68909d0a5d34, from Nov 15, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.GSterlingPress/fresh/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.GSterlingPress/fresh
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.GSterlingPress/fresh.svg)](https://radar.anlyon.com/servers/io.github.GSterlingPress/fresh)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.

FRESH — Shared URL Freshness Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FRESH — Shared URL Freshness Intelligence MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FRESH — Shared URL Freshness Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FRESH — Shared URL Freshness Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FRESH — Shared URL Freshness Intelligence MCP server have?

2 tools: 1 write, 1 read. fresh_observe and fresh_check.

Does the FRESH — Shared URL Freshness Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FRESH — Shared URL Freshness Intelligence MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fresh_check and fresh_observe.

Has the FRESH — Shared URL Freshness Intelligence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.