_ registry / mcp + a2a streamable-http · checked 2h ago

fresh-feeds

https://fresh-feeds.foomworks.workers.dev

Registry code: 1e3cd7db598c9a15

api record

Free tools (search_mcp_registry, get_registry_highlights, verify_mcp_server, list_x402_services, feeds_status, assess_agent_risk) return data directly. Tools named get_*_snapshot / get_registry_changes / verify_mcp_server_report return x402 payment instructions for the full paid data (no account; USDC on Base, <= $0.05/call).

endpoint
https://fresh-feeds.foomworks.workers.dev/mcp
door code
7dbcfc4c9fbf5580
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is fresh-feeds live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is fresh-feeds free to use?
Yes — the hub reached it with no key and no payment.
What tools does fresh-feeds have?
10 tools: verify_mcp_server, assess_agent_risk, verify_mcp_server_report, list_x402_services, get_registry_highlights, get_x402_services_snapshot, search_mcp_registry, feeds_status, ….
Is fresh-feeds safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.3%· all time 99.5%

latency
158ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1807 checks · signed record
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
developer tools apis & integration
used for
  • search a registry of mcp servers
  • verify an mcp server's trust grade
  • list live x402 services
  • assess an agent for fraud risk
takes → gives
text → data
tools
10 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 3 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
5

distinct

settlements
10

last 2026-11-04

received on chain
0.38 USDC

no flags

_ what it can do 10 tools
7 open 3 never probed 7 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_x402_services reads open 4h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "max results 1-25 (default 10)"
    },
    "payable_only": {
      "type": "boolean",
      "description": "only services currently returning 402 (payable right now)"
    }
  }
}
    arguments 15 lines
  • get_registry_highlights reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_x402_services_snapshot reads open 7h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_mcp_registry reads open 14h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "max results 1-25 (default 10)"
    },
    "query": {
      "type": "string",
      "description": "case-insensitive substring matched against server name/title/description; omit for the top servers by quality score"
    }
  }
}
    arguments 15 lines
  • feeds_status reads open 4h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_registry_changes reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "description": "baseline date YYYY-MM-DD (see feeds_status for available dates)"
    }
  }
}
    arguments 9 lines
  • get_mcp_registry_snapshot reads open 4h ago

    PAID (x402): returns x402 payment instructions for the FULL deduped, quality-scored MCP registry snapshot. Use search_mcp_registry (free) for targeted lookups.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • verify_mcp_server reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "server"
  ],
  "properties": {
    "server": {
      "type": "string",
      "description": "MCP registry server name (use search_mcp_registry to find one)"
    }
  }
}
    arguments 12 lines
  • assess_agent_risk reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "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": {
      "type": "integer",
      "minimum": 1,
      "description": "ERC-8004 Identity tokenId on Base; omit to list the maintained sample"
    }
  }
}
    arguments 14 lines
  • verify_mcp_server_report reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "server"
  ],
  "properties": {
    "server": {
      "type": "string",
      "description": "MCP registry server name"
    }
  }
}
    arguments 12 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1e3cd7db598c9a15.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1e3cd7db598c9a15/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1e3cd7db598c9a15/badge.svg)](https://brick.blue/agent/1e3cd7db598c9a15?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.