---
name: fresh-feeds.foomworks.workers.dev
description: fresh-feeds.foomworks.workers.dev provides two snapshot-style discovery feeds: one cataloging recently updated x402 payment-gated services with liveness and pricing data, and one diffing the MCP server registry to surface added, removed, or changed entries since a given date. Both endpoints return point-in-time snapshots rather than streaming or full-catalog data.
host: fresh-feeds.foomworks.workers.dev
---

# fresh-feeds.foomworks.workers.dev

This host serves agents that need to discover or monitor the x402 and MCP ecosystems. It covers two distinct registries: the x402 payment-gated API catalog (with liveness probing and payment route metadata) and the MCP server registry (with change-diff capability). It is not a general-purpose data API or real-time feed; it is narrowly focused on ecosystem discovery and change detection for these two protocol spaces.

## When to use this host

Use this host when an agent needs to discover currently live x402 payment-gated services and inspect their pricing or payment routes, or when it needs to detect changes in the MCP server registry since a known date. Do not use it for full-catalog retrieval of x402 resources (the feed covers only a recently updated subset of 25,000+ total entries), for real-time or streaming data, or for fetching the complete current state of the MCP registry. For full x402 catalog access, look for a host exposing a paginated or bulk catalog endpoint. For static MCP registry snapshots, look for a host serving the full registry state rather than a delta.

## Capabilities

### x402 Service Discovery

Retrieves a liveness-probed snapshot of recently updated x402 payment-gated services, including resource URLs, pricing, and payment routes, enabling agents to find and evaluate available x402-compatible APIs.

- **`fetch-x402-services-feed`** — Returns a liveness-probed catalog of x402 payment-gated services including resource URLs, pricing, payment routes, and current HTTP liveness status.

### MCP Registry Monitoring

Returns a dated diff of the MCP server registry, identifying added, removed, and changed server entries since a specified baseline, enabling agents to track ecosystem churn and discover new integrations.

- **`fetch-mcp-registry-changes`** — Returns a dated diff of the MCP registry showing added, removed, and changed server entries since a specified baseline date.

## Skill reference

### `fetch-x402-services-feed`

**x402 Services Feed** — Returns a liveness-probed catalog of x402 payment-gated services including resource URLs, pricing, payment routes, and current HTTP liveness status.

*Use when:* Use when an agent needs to discover available x402-compatible APIs, check which services are currently alive and demanding payment, or inspect pricing and payment routes for services in the x402 discovery catalog.

*Not for:* Do not use for real-time price feeds or streaming data; this is a single-shot snapshot of recently updated catalog entries. Do not use to retrieve the full catalog of 25,000+ resources — this feed covers only the most recently updated subset.

**Inputs:**

- `If-None-Match` (string) — ETag value from a prior response. If the feed has not changed, the server returns HTTP 304 Not Modified at no charge, avoiding a repeat payment.

**Returns:** Returns a JSON object with feed metadata (catalogTotal, count, alive counts) and a services array of up to ~842 entries each containing resource URL, description, multi-network payment options, and liveness probe results.

**Example:** `GET https://fresh-feeds.foomworks.workers.dev/feeds/x402-services`

---

### `fetch-mcp-registry-changes`

**MCP Registry Changes** — Returns a dated diff of the MCP registry showing added, removed, and changed server entries since a specified baseline date.

*Use when:* Use when an agent needs to detect newly published, removed, or updated MCP servers in the registry since a given date, such as for monitoring registry churn or discovering new MCP integrations.

*Not for:* Do not use for retrieving the full current state of the MCP registry; this endpoint only returns a delta (diff) relative to a baseline date.

**Inputs:**

- `since` (string) — Baseline date in YYYY-MM-DD format. If omitted, the diff is computed from the oldest available baseline date.

**Returns:** Returns a JSON object with feed metadata, since/until timestamps, a counts summary (added/removed/changed/total), and arrays of added, removed, and changed MCP server entries.

**Example:** `GET https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes?since=2026-07-01`

---