Skip to content

fresh-feeds — trending/new/changed MCP servers + x402 change-data API

io.github.foomworks/fresh-feedsfoomworksstreamable-httpv1.2.0Scanned

Trending/new/changed MCP servers: a liveness-probed freshness index + x402-paid change-data API

10 tools: 3 change things and 7 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 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 fresh-feeds — trending/new/changed MCP servers + x402 change-data API can do

The fresh-feeds — trending/new/changed MCP servers + x402 change-data API is published by the GitHub account foomworks. It has 10 tools. It can create or change data (3 tools: verify_mcp_server, assess_agent_risk and verify_mcp_server_report), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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 19, 2026, version 1.2.0.

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.

10 tools

Changes things 3Claude Code: ask
  • assess_agent_riskVerify-before-you-pay: a read-only fraud/impersonation RISK assessment (0-100, higher = riskier) for an ERC-8004 agent on Base, cross-referencing its DECLARED identity (agent-card)…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify-before-you-pay: a read-only fraud/impersonation RISK assessment (0-100, higher = riskier) for an ERC-8004 agent on Base, cross-referencing its DECLARED identity (agent-card) against on-chain control (ownerOf). Flags owner-mismatch, registration-inconsistency, off-chain/unproven cards, dead endpoints, and orphaned identities. Free; from a maintained sample of the first agentIds. Look up by tokenId (agentId) OR by the counterparty wallet/payTo you're about to pay (address — 0x… or eip155:8453:0x…). Omit both to list the sample (riskiest first).
  • verify_mcp_serverFree preview-grade trust report for one registry MCP server: a transparent 0-100 grade from cached signals (registry status, endpoint presence, freshness).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Free preview-grade trust report for one registry MCP server: a transparent 0-100 grade from cached signals (registry status, endpoint presence, freshness). The full report with a LIVE endpoint reachability probe + component breakdown is paid (verify_mcp_server_report, x402).
  • verify_mcp_server_reportPAID (x402): returns x402 payment instructions for the FULL verification report (LIVE endpoint probe + component breakdown) for one registry MCP server.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (x402): returns x402 payment instructions for the FULL verification report (LIVE endpoint probe + component breakdown) for one registry MCP server.
Only reads 7Show 7 read-only tools
  • feeds_statusFreshness/health of both feeds (snapshot ages, counts, available change-baseline dates).No findings

    Why it is in this group

    • The name "feeds_status" says "status": a word for reading.
    Description, as the server wrote it
    Freshness/health of both feeds (snapshot ages, counts, available change-baseline dates). Free.
  • get_mcp_registry_snapshotPAID (x402): returns x402 payment instructions for the FULL deduped, quality-scored MCP registry snapshot.No findings

    Why it is in this group

    • The name "get_mcp_registry_snapshot" says "get": a word for reading.
    Description, as the server wrote it
    PAID (x402): returns x402 payment instructions for the FULL deduped, quality-scored MCP registry snapshot. Use search_mcp_registry (free) for targeted lookups.
  • get_registry_changesPAID (x402): returns x402 payment instructions for the registry delta (added/removed/changed servers) since a daily baseline — the cheap habit endpoint for repeat callers.No findings

    Why it is in this group

    • The name "get_registry_changes" says "get": a word for reading.
    Description, as the server wrote it
    PAID (x402): returns x402 payment instructions for the registry delta (added/removed/changed servers) since a daily baseline — the cheap habit endpoint for repeat callers.
  • get_registry_highlightsTop 10 MCP servers by quality score + trending (new arrivals / score risers) + snapshot freshness.No findings

    Why it is in this group

    • The name "get_registry_highlights" says "get": a word for reading.
    Description, as the server wrote it
    Top 10 MCP servers by quality score + trending (new arrivals / score risers) + snapshot freshness. Free.
  • get_x402_services_snapshotPAID (x402): returns x402 payment instructions for the FULL liveness-probed x402 services feed.No findings

    Why it is in this group

    • The name "get_x402_services_snapshot" says "get": a word for reading.
    Description, as the server wrote it
    PAID (x402): returns x402 payment instructions for the FULL liveness-probed x402 services feed.
  • list_x402_servicesList the x402 services discovery catalog's active edge, liveness-probed: know a service is up and correctly demanding payment before you pay it.No findings

    Why it is in this group

    • The name "list_x402_services" says "list": a word for reading.
    Description, as the server wrote it
    List the x402 services discovery catalog's active edge, liveness-probed: know a service is up and correctly demanding payment before you pay it. Free; up to 25. For the full liveness-probed feed use get_x402_services_snapshot (paid, x402).
  • search_mcp_registrySearch the continuously-maintained MCP server registry (deduped, quality-scored, refreshed every 30 min) by name/title/description.No findings

    Why it is in this group

    • The name "search_mcp_registry" says "search": a word for reading.
    Description, as the server wrote it
    Search the continuously-maintained MCP server registry (deduped, quality-scored, refreshed every 30 min) by name/title/description. Free; returns up to 25 matching servers with score, status, remotes and packages. For the FULL corpus (~1500 servers) use get_mcp_registry_snapshot (paid, x402).

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:04 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
3
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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://fresh-feeds.foomworks.workers.dev/mcp: tools/list returned 10 tools to an anonymous client, including verify_mcp_server (write), assess_agent_risk (write), verify_mcp_server_report (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 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fresh-feeds https://fresh-feeds.foomworks.workers.dev/mcp
claude mcp add --transport http fresh-feeds https://fresh-feeds.foomworks.workers.dev/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": [
      "mcp__fresh-feeds__search_mcp_registry",
      "mcp__fresh-feeds__get_registry_highlights",
      "mcp__fresh-feeds__list_x402_services",
      "mcp__fresh-feeds__feeds_status",
      "mcp__fresh-feeds__get_mcp_registry_snapshot",
      "mcp__fresh-feeds__get_registry_changes",
      "mcp__fresh-feeds__get_x402_services_snapshot"
    ],
    "ask": [
      "mcp__fresh-feeds__verify_mcp_server",
      "mcp__fresh-feeds__assess_agent_risk",
      "mcp__fresh-feeds__verify_mcp_server_report"
    ],
    "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-feeds. Review it before you use it.

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.foomworks/fresh-feeds/verify?hash=85e35adacb572fae92289608cb38839c517e5f2eec9081bfc6d55a2b63deab87" | jq -e '.changed == false'

Pinned hash 85e35adacb57, from Nov 19, 2026, 17: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.foomworks/fresh-feeds/changes.xml

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

Badge

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

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

fresh-feeds — trending/new/changed MCP servers + x402 change-data API: questions and answers

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

Is the fresh-feeds — trending/new/changed MCP servers + x402 change-data API safe?

No scan can promise that. What its definitions show: 10 tools, 3 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-feeds — trending/new/changed MCP servers + x402 change-data API delete data?

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

Can the fresh-feeds — trending/new/changed MCP servers + x402 change-data API 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-feeds — trending/new/changed MCP servers + x402 change-data API have?

10 tools: 3 write, 7 read. verify_mcp_server, assess_agent_risk, verify_mcp_server_report, search_mcp_registry, get_registry_highlights, list_x402_services, feeds_status, get_mcp_registry_snapshot and 2 more.

Does the fresh-feeds — trending/new/changed MCP servers + x402 change-data API need sign-in or OAuth?

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

Does the fresh-feeds — trending/new/changed MCP servers + x402 change-data API send data to outside services?

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

Has the fresh-feeds — trending/new/changed MCP servers + x402 change-data API changed its tools?

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