Skip to content

Freshness Validator MCP server

com.myuiaf/freshness-validatormyuiaf.comstreamable-httpv1.0.1Scanned

Flags when an AI agent's context is stale: freshness score 0-100 and source change detection.

2 tools: 2 change things.

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

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • 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 Freshness Validator MCP server can do

The Freshness Validator MCP server is published by myuiaf.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: validate and register_source), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (validate and register_source).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 8, 2026, version 1.0.1.

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 2Claude Code: ask
  • register_sourceRegister a public https URL for ongoing freshness monitoring.Reads text others writeNo 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.
    Description, as the server wrote it
    Register a public https URL for ongoing freshness monitoring. The page is fetched once immediately as a baseline. Costs twice the per-call rate; registering the same URL again only updates its frequency.

    Annotations the server declares

    • title: Monitor a source page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • validateCheck how fresh a piece of context is.Reads text others write1 finding

    Why it is in this group

    • The name "validate" says "validate": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "validate" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "validate" says "validate": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Check how fresh a piece of context is. Returns a score from 0 to 100, a stale flag (score below 70), flagged issues, and suggestions. Register the source first with register_source to enable change detection and content matching. Billed per call.

    Annotations the server declares

    • title: Check context freshness
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • 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 or outbound.

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 out0
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.

Sign-in required, OAuth metadata published

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://api.myuiaf.com/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://api.myuiaf.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.myuiaf.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "validate" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "validate" says "validate": a word for reading.

    What this check looks for

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 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http freshness-validator https://api.myuiaf.com/mcp
claude mcp add --transport http freshness-validator https://api.myuiaf.com/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__freshness-validator__validate",
      "mcp__freshness-validator__register_source"
    ],
    "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 freshness-validator. Review it before you use it.

Capability tags behind 2 rules
  • mcp__freshness-validator__validate untrusted-input
  • mcp__freshness-validator__register_source untrusted-input

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/com.myuiaf/freshness-validator/verify?hash=2d23d56f1702726f11ae8c8195a742945357630277120f98889c21ddda78805d" | jq -e '.changed == false'

Pinned hash 2d23d56f1702, from Nov 8, 2026, 08:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.myuiaf/freshness-validator/changes.xml

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

Badge

Anlyon Radar badge for com.myuiaf/freshness-validator
[![Anlyon Radar](https://radar.anlyon.com/badge/com.myuiaf/freshness-validator.svg)](https://radar.anlyon.com/servers/com.myuiaf/freshness-validator)

Source: MCP Registry. Synced Nov 13, 2026, 01:17 UTC.

Freshness Validator MCP server: questions and answers

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

Is the Freshness Validator MCP server safe?

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

Can the Freshness Validator MCP server delete data?

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

Can the Freshness Validator 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 Freshness Validator MCP server have?

2 tools: 2 write. validate and register_source.

Does the Freshness Validator MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Freshness Validator MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Freshness Validator MCP server changed its tools?

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