# fresh-feeds — trending/new/changed MCP servers + x402 change-data API (remote · fresh-feeds.foomworks.workers.dev)

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

- Trust score: 60/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `fresh-feeds.foomworks.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/foomworks-fresh-feeds/fresh-feeds.md), [page](https://verifymcp.io/servers/foomworks-fresh-feeds/fresh-feeds)

## Channel facts

- Endpoint: `https://fresh-feeds.foomworks.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 879 tokens (~87/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http foomworks-fresh-feeds https://fresh-feeds.foomworks.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.foomworks-fresh-feeds]
url = "https://fresh-feeds.foomworks.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "foomworks-fresh-feeds": {
      "type": "remote",
      "url": "https://fresh-feeds.foomworks.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add foomworks-fresh-feeds --url https://fresh-feeds.foomworks.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  foomworks-fresh-feeds:
    url: "https://fresh-feeds.foomworks.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "foomworks-fresh-feeds": {
      "type": "http",
      "url": "https://fresh-feeds.foomworks.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 58, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (10)

### `search_mcp_registry` (~123 tokens)

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

Input parameters:

- `limit` (integer): max results 1-25 (default 10)
- `query` (string): case-insensitive substring matched against server name/title/description; omit for the top servers by quality score

### `get_registry_highlights` (~34 tokens)

Top 10 MCP servers by quality score + trending (new arrivals / score risers) + snapshot freshness. Free.

### `verify_mcp_server` (~85 tokens)

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

Input parameters:

- `server` (string, required): MCP registry server name (use search_mcp_registry to find one)

### `list_x402_services` (~103 tokens)

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

Input parameters:

- `limit` (integer): max results 1-25 (default 10)
- `payable_only` (boolean): only services currently returning 402 (payable right now)

### `feeds_status` (~29 tokens)

Freshness/health of both feeds (snapshot ages, counts, available change-baseline dates). Free.

### `assess_agent_risk` (~225 tokens)

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

Input parameters:

- `address` (string): the wallet/payTo you're about to transact with (0x… or CAIP-10 eip155:8453:0x…); resolves to the matching agent(s)' risk in the sample
- `agentId` (integer): ERC-8004 Identity tokenId on Base; omit to list the maintained sample

### `get_mcp_registry_snapshot` (~49 tokens)

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_changes` (~64 tokens)

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.

Input parameters:

- `since` (string): baseline date YYYY-MM-DD (see feeds_status for available dates)

### `get_x402_services_snapshot` (~34 tokens)

PAID (x402): returns x402 payment instructions for the FULL liveness-probed x402 services feed.

### `verify_mcp_server_report` (~52 tokens)

PAID (x402): returns x402 payment instructions for the FULL verification report (LIVE endpoint probe + component breakdown) for one registry MCP server.

Input parameters:

- `server` (string, required): MCP registry server name

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/foomworks-fresh-feeds/fresh-feeds#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 58
- 2026-07-30: 60
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://fresh-feeds.foomworks.workers.dev/mcp
- Repository: https://github.com/foomworks/fresh-feeds
- Website: https://foomworks.app/fresh-feeds/
- Changelog RSS feed: https://verifymcp.io/servers/foomworks-fresh-feeds/fresh-feeds/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/foomworks-fresh-feeds/fresh-feeds/changelog.json
- HTML version of this page: https://verifymcp.io/servers/foomworks-fresh-feeds/fresh-feeds