75trust / 100

Mcp Registry Changes

by fresh-feeds in Other

x402 APIPassing, checked 4 h ago

Delta of the MCP registry since a daily baseline: added, removed, and changed (score/status) servers — the cheap habit endpoint for repeat callers.

GET
https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
424 ms
609 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes

Each call costs $0.02 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes

Example response

The provider's example. We can't check it without paying.

Example response, 36 lines
{
  "added": [
    {
      "name": "org.example/new-server",
      "score": 6
    }
  ],
  "changed": [
    {
      "after": {
        "score": 7,
        "status": "active"
      },
      "before": {
        "score": 5,
        "status": "active"
      },
      "name": "org.example/server"
    }
  ],
  "counts": {
    "added": 3,
    "changed": 12,
    "removed": 1,
    "total": 1548
  },
  "feed": "mcp-registry",
  "removed": [
    {
      "name": "org.example/old-server",
      "score": 2
    }
  ],
  "since": "2026-06-09",
  "until": "2026-06-10T07:22:52.782Z"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ffresh-feeds.foomworks.workers.dev%2Ffeeds%2Fmcp-registry%2Fchanges
const res = await pay("https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://fresh-feeds.foomworks.workers.dev/feeds/mcp-registry/changes")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402120 ms$0.02
9 h agoPassed40296 ms$0.02
14 h agoPassed402395 ms$0.02
19 h agoPassed402291 ms$0.02
23 h agoPassed402408 ms$0.02
Show 10 older checks
28 h agoPassed402420 ms$0.02
32 h agoPassed402129 ms$0.02
36 h agoPassed402575 ms$0.02
40 h agoPassed402368 ms$0.02
44 h agoPassed402451 ms$0.02
2 days agoPassed402327 ms$0.02
2 days agoPassed402553 ms$0.02
2 days agoPassed40290 ms$0.02
3 days agoPassed402291 ms$0.02
3 days agoPassed402167 ms$0.02