fresh-feeds — trending/new/changed MCP servers + x402 change-data API
REMOTE · FRESH-FEEDS.FOOMWORKS.WORKERS.DEV · SCANNED AUG 3
Trending/new/changed MCP servers: a liveness-probed freshness index + x402-paid change-data API
Available components
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. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 879 tokens (~87/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · fresh-feeds.foomworks.workers.dev
claude mcp add --transport http foomworks-fresh-feeds https://fresh-feeds.foomworks.workers.dev/mcp
[mcp_servers.foomworks-fresh-feeds] url = "https://fresh-feeds.foomworks.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"foomworks-fresh-feeds": {
"type": "remote",
"url": "https://fresh-feeds.foomworks.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add foomworks-fresh-feeds --url https://fresh-feeds.foomworks.workers.dev/mcp --transport streamable-http
mcp_servers:
foomworks-fresh-feeds:
url: "https://fresh-feeds.foomworks.workers.dev/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://fresh-feeds.foomworks.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foomworks.workers.dev | CN=WE1,O=Google Trust Services,C=US | 10 Jun 2026 | 8 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | bb98b43357bcaea70e70e4667ecce3be |
| SANs: foomworks.workers.dev, *.foomworks.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of fresh-feeds.foomworks.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fresh-feeds.foomworks.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://fresh-feeds.foomworks.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
assess_agent_risk ~225
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
feeds_status ~29
Freshness/health of both feeds (snapshot ages, counts, available change-baseline dates). Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mcp_registry_snapshot ~49
PAID (x402): returns x402 payment instructions for the FULL deduped, quality-scored MCP registry snapshot. Use search_mcp_registry (free) for targeted lookups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_registry_changes ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | — | baseline date YYYY-MM-DD (see feeds_status for available dates) |
No output schema declared.
No examples provided.
get_registry_highlights ~34
Top 10 MCP servers by quality score + trending (new arrivals / score risers) + snapshot freshness. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_x402_services_snapshot ~34
PAID (x402): returns x402 payment instructions for the FULL liveness-probed x402 services feed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_x402_services ~103
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | max results 1-25 (default 10) |
| payable_only | boolean | — | only services currently returning 402 (payable right now) |
No output schema declared.
No examples provided.
search_mcp_registry ~123
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
verify_mcp_server ~85
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).
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | MCP registry server name (use search_mcp_registry to find one) |
No output schema declared.
No examples provided.
verify_mcp_server_report ~52
PAID (x402): returns x402 payment instructions for the FULL verification report (LIVE endpoint probe + component breakdown) for one registry MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | MCP registry server name |
No output schema declared.
No examples provided.