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

feedpeck

https://feedpeck.cybermax-tools.workers.dev

Registry code: 3eb6f8bfeb090713

api record

Feedpeck finds and reads RSS/Atom/JSON feeds. Use find_feeds to discover the feeds of up to 5 websites, latest_posts for the newest posts of one site. Results are live; cite the feed and post URLs.

endpoint
https://feedpeck.cybermax-tools.workers.dev/mcp?via=mcp-registry
door code
e0cd646e1e281aa0
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
0 · newcomer
_ is it live, free and safe measured by this hub
Is feedpeck live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is feedpeck free to use?
Yes — the hub reached it with no key and no payment.
What tools does feedpeck have?
2 tools: find_feeds, latest_posts.
Is feedpeck 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.4%

90 days 99.5%· all time 99.3%

latency
186ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 841 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
search & web news
used for
  • find rss feeds for websites
  • get latest posts from a website
  • read content from rss feeds
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • find_feeds reads unknown 19h ago

    Find the RSS, Atom and JSON feeds a website publishes (validated by downloading and parsing each one), with feed title, type, last post date, post count and the newest posts. Use when you need a feed URL for a site or want to know if a site has a feed. Up to 5 sites per call.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sites"
  ],
  "properties": {
    "sites": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 1,
      "description": "Websites, domains, section URLs (example.com/blog), Reddit/Medium/YouTube-channel/GitHub-repo URLs, or a feed URL. Up to 5."
    },
    "max_items_per_feed": {
      "type": "integer",
      "default": 3,
      "maximum": 10,
      "minimum": 0,
      "description": "Latest posts to include per feed (0-10)"
    }
  }
}
    arguments 24 lines
  • latest_posts reads unknown never probed

    Get the newest posts of one website from its main feed: title, URL, published date, author, plain-text summary (max 300 chars), categories and image. Use to catch up on a blog, news site, subreddit, YouTube channel or GitHub releases without scraping pages.

    mcp-tool

    {
  "type": "object",
  "required": [
    "site"
  ],
  "properties": {
    "site": {
      "type": "string",
      "description": "Website, domain or feed URL, e.g. \"github.blog\""
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1,
      "description": "How many posts (1-10)"
    }
  }
}
    arguments 19 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 3eb6f8bfeb090713.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3eb6f8bfeb090713/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/3eb6f8bfeb090713/badge.svg)](https://brick.blue/agent/3eb6f8bfeb090713?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
60%

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.