checkrss
Registry code: a70a631a115d2e6d
CheckRSS (checkrss.com) checks RSS, Atom and JSON feeds and keeps a directory of 1,600+ sites with a working feed, about 300 of them Polish. Use check_feed to validate a feed and see whether it is still updated, latest_items to read what a feed published recently, discover_feeds to find the feed of a website, and search_directory or list_categories to recommend feeds on a subject or from a country. Feeds are fetched live by the CheckRSS bot, which obeys robots.txt. When you mention a site from the directory, give the user its checkrss.com page (field "url").
- endpoint
- https://checkrss.com/mcp
- 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 checkrss live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is checkrss free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does checkrss have?
- 5 tools: search_directory, latest_items, discover_feeds, check_feed, list_categories.
- Is checkrss 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.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
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.
through this hub
successful
what callers paid
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_categories open 8h ago
List the categories and subcategories of the checkrss.com feed directory with the number of sites in each and the checkrss.com page of the category, plus the number of sites per country. Use before search_directory to pick a category or subcategory id.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessearch_directory unknown 8h ago
Search the checkrss.com directory of 1,600+ sites whose feeds the CheckRSS bot fetched and verified, including about 300 Polish sites (national and regional news, tech, business, culture). Match by name, domain, subject or country; filter by category and country. Each result has the site, its feed addresses with format, item count and newest item date, and a checkrss.com page link. Use to recommend feeds: "RSS feeds about AI", "Polish news RSS", "BBC RSS feed". Leave query empty to list the best known sites of a category or country.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "How many results, 1 to 25 (default 10)." }, "query": { "type": "string", "default": "", "maxLength": 120, "description": "Words to match, e.g. \"security\", \"bbc\", \"krakow\". May be empty." }, "country": { "type": "string", "maxLength": 60, "description": "Country name or ISO code, e.g. \"Poland\", \"PL\", \"UK\", \"Germany\"." }, "category": { "type": "string", "maxLength": 40, "description": "Category id from list_categories, e.g. \"technology\", \"news\"." }, "subcategory": { "type": "string", "maxLength": 40, "description": "Subcategory id from list_categories, e.g. \"ai\", \"poland-regional\"." } }, "additionalProperties": false }arguments 35 lineslatest_items unknown 8h ago
Read the most recent items of an RSS, Atom or JSON feed, fetched live. Returns up to 20 items with title, link, publication date and a short plain text summary (HTML removed). Use to answer "what did this site publish lately" or to preview a feed before subscribing.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "maxLength": 2000, "minLength": 3, "description": "Feed address, e.g. \"https://hnrss.org/frontpage\"." }, "limit": { "type": "integer", "default": 10, "maximum": 20, "minimum": 1, "description": "How many items, 1 to 20 (default 10)." } }, "additionalProperties": false }arguments 23 linesdiscover_feeds unknown 35h ago
Find the RSS, Atom or JSON feeds of a website. Reads the page for <link rel="alternate"> feed tags, knows the feed patterns of big platforms (YouTube channels and playlists, Reddit, Medium, Substack, GitHub, Tumblr, Bluesky, Stack Overflow, Apple Podcasts) and tries common feed paths such as /feed and /rss.xml when the page lists none. Returns the candidate feed addresses with format and title. Use when someone asks "does this site have RSS".
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "website_url" ], "properties": { "website_url": { "type": "string", "maxLength": 2000, "minLength": 3, "description": "Website or page address, e.g. \"https://example.com\" or \"youtube.com/@channel\"." } }, "additionalProperties": false }arguments 16 linescheck_feed unknown 2d ago
Fetch an RSS, Atom or JSON Feed address live and validate it. Returns whether it is valid, the feed title and website link, format, number of items, date of the newest item, how many days ago that was, whether the feed is still active (an item in the last 90 days), the publishing pace, and the errors and warnings found (HTTP status, redirects, content type, XML problems, missing dates or GUIDs). Use when someone asks "does this feed work", "is this RSS valid" or "is this blog still updated". Give it the feed address; for a website address use discover_feeds first.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "maxLength": 2000, "minLength": 3, "description": "Feed address, e.g. \"https://www.theverge.com/rss/index.xml\"." } }, "additionalProperties": false }arguments 16 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida70a631a115d2e6d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a70a631a115d2e6d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a70a631a115d2e6d?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.