_ registry / mcp http-sse · checked 1h ago

rss-feed

https://rss-feed.dsh.sh

Registry code: dba611275f557cc2

api record

RSS, Atom and JSON feeds for agents: find a site's feed, read items as JSON, keyless news search. Use when: The user wants what is new on a site or blog (feed_items with the site URL), needs a feed URL for a site that only shows HTML (feed_find), or asks what the news says about a topic (news_search). Use instead of scraping listing pages by hand. Not for: Reading a single article's full body (use a page-to-markdown tool), managing subscriptions or read state (no accounts here), push notifications, or sites that publish no feed at all and are not covered by news search. Every tool takes…

endpoint
https://rss-feed.dsh.sh/mcp
protocol
http-sse ·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 rss-feed live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is rss-feed free to use?
Yes — the hub reached it with no key and no payment.
What tools does rss-feed have?
3 tools: news_search, feed_find, feed_items.
Is rss-feed 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%

90 days 99.1%· all time 99.1%

latency
502ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 343 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • find the rss feed of a website
  • read latest feed items as json
  • search news on a topic
takes → gives
text, web pages → data
tools
3 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 3 tools
3 never probed 0 of 3 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.

  • news_search reads unknown 12h ago

    Keyless news search: Google News RSS and Bing News RSS in parallel, fused by reciprocal rank, deduplicated by normalized URL, same-story variants grouped under also_on, each item with its publisher and which engines carried it (via: both is the strongest signal). Use for "what is the news about X"; use feed_items for one site's own posts.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query",
        "task_context"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "default": "en",
          "maxLength": 5,
          "minLength": 2,
          "description": "Google News hl language, e.g. en, de."
        },
        "when": {
          "enum": [
            "1h",
            "1d",
            "7d",
            "30d"
          ],
          "type": "string",
          "description": "Recency window (Google News honours it; Bing News has no such knob and is queried as-is)."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "News query; at least 2 characters (a 1-char query returns unrelated noise from the engines)"
        },
        "region": {
          "type": "string",
          "default": "US",
          "maxLength": 2,
          "minLength": 2,
          "description": "Google News gl region, e.g. US, GB."
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 52 lines
  • feed_find reads unknown 12h ago

    Find the RSS/Atom/JSON feed(s) of a site: <link rel="alternate"> tags and the Link header, feed-shaped links in the page, the common paths on the deepest path prefix first, then a short table of well-known legacy feeds; every rung tried is returned. Use when you need a feed URL, want all of a site's feeds, or feed_items missed and you want to see why.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "site",
        "task_context"
      ],
      "properties": {
        "all": {
          "type": "boolean",
          "default": false,
          "description": "Keep going after the first feed to list every feed found (costs more fetches)."
        },
        "site": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 3,
          "description": "Site or page URL, e.g. \"arstechnica.com\" or \"https://vercel.com/blog\"."
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 27 lines
  • feed_items reads unknown 12h ago

    Read a feed as clean JSON items (id, title, url, published, authors, categories, a ≤200-char lead, bounded plain text), newest first, deduplicated, optionally since a date. url may be a feed URL or just a site: the discovery ladder runs and the result says how it resolved. Use for "what is new on X".

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "url",
        "task_context"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 3,
          "description": "Feed URL, or a site/page URL to discover the feed for."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1
        },
        "since": {
          "type": "string",
          "maxLength": 40,
          "description": "ISO date/time; only items published or updated after it."
        },
        "max_chars": {
          "type": "integer",
          "default": 30000,
          "maximum": 200000,
          "minimum": 1000,
          "description": "Total budget for content_text across the returned items."
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 40 lines
_ try it 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 dba611275f557cc2.

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

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.

_ also on dsh.sh 4 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.