rssamplifier
MCP server giving AI agents search and access to a directory of blogs and feeds
Answered our latest tool-list check 3 hours ago with 29 tools. It will be marked verified after 3 successful checks in 7 days.
- Platforms
- Web, CLI, API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About rssamplifier
rssamplifier is an MCP server for web search and scraping. It runs as a hosted remote server, so there is nothing to install locally.
The README and site describe RSSAmp as an open directory where each blog gets its own page with recent summaries. Feeds are added by submitting a URL, a list of URLs, or an OPML file, and the service locates the feed and reads it. The directory is also published as JSON, OPML and plain text so that scripts and language models can consume it directly.
The MCP registry entry points to a streamable HTTP endpoint at the site's /api/mcp path, so an AI client can connect to it as a remote server. The site also offers a command-line installer, which covers finding feeds by subject, searching posts and exporting OPML from a shell.
It suits people who maintain reading lists or research sources across many small sites, and developers building agents that need to discover blogs and pull their latest posts.
Install
Run in a terminal
claude mcp add --transport http rssamplifier https://rssamp.com/api/mcpAdd to Settings → Connectors → Add custom connector
https://rssamp.com/api/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"rssamplifier": {
"url": "https://rssamp.com/api/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"rssamplifier": {
"type": "http",
"url": "https://rssamp.com/api/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"rssamplifier": {
"serverUrl": "https://rssamp.com/api/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://rssamp.com/api/mcpEnter a Name (for example "rssamplifier"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"rssamplifier": {
"type": "http",
"url": "https://rssamp.com/api/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (29)
Read directly from the server.
21 of 29 tools say they're read-only. 8 of 29 tools say they can delete or change data.
From the server's own tool annotations; not verified by us.
- searchSays read-only
- Full-text search across every post and blog in the directory. Returns matching blogs and matching individual posts, each with the identifiers read_post needs. Use mode="any" to match any one of the terms rather than all of them — useful when a thing goes by several names. The directory is mostly blogs, so the best-ranked results for anything are usually blog posts: every reply counts the whole mat
- list_feedsSays read-only
- Page through the whole directory, newest first. Narrow to one category with kind: blog, news, podcast, music, video, comic, live or reel. The category is decided from the feed document on every crawl, never from what the submitter claimed.
- get_feedSays read-only
- One blog or podcast: its metadata, who writes it, where it can be found elsewhere, the topics it is filed under — including the ones no other feed shares — and its recent posts. `authors` is people; `links` is the blog's own accounts, which is what an unsigned blog has instead. Each post carries the feed slug and guid that read_post takes. Use the slug from search or list_feeds, not the site's own
- list_topicsSays read-only
- What the directory covers, by how many feeds cover it. Pass query to search the index instead of paging it. Only subjects at least two feeds share are indexed — a topic one blog uses is that blog's own vocabulary, and lives on its page instead. Raise min to find the well-covered subjects.
- get_topicSays read-only
- Every feed filed under one topic. The keyword is normalised, so "Home Lab", "home lab" and "home-lab" all reach the same topic and you can pass a phrase you read anywhere. Each feed says whether it landed here from the publisher's own tag or from a phrase counted across its writing. A comma-separated list ("business, saas, crypto", up to 10) returns the union: every feed filed under any of them, e
- topic_postsSays read-only
- What the feeds covering a topic have actually published lately, newest first — the river rather than the roster. Note the difference from get_topic, which lists who covers the subject; this lists what they wrote. Drawn from the feeds most strongly filed under the topic, so a very broad keyword is a sample rather than a census. A comma-separated list ("business, saas, crypto", up to 10) is one rive
- read_postSays read-only
- The full text of one post, extracted from the publisher's own page and returned as prose. Takes the feed slug and post guid that search, get_feed and topic_posts return. The first reader pays for the fetch and everyone after them reads it out of the database, so the publisher is asked once rather than once per view. A post behind a paywall, on a site that is down, or by a publisher who asked not t
- random_feedSays read-only
- One feed from the directory, chosen at random, with its recent posts. The web without a ranking function: what is here rather than what is popular.
- list_authorsSays read-only
- The directory's authors and where else they publish — their own sites, Mastodon and Bluesky accounts, GitHub, links pages. Every link was published by the author on their own site as a rel="me" claim, an h-card or JSON-LD; nothing is scraped from a platform or bought. Filter with network to find only people reachable a given way (email, fediverse, bluesky, github, website, linktree), or query to s
- get_authorSays read-only
- One person: where to find them, and everything in the directory they publish. The feed list is what settles whether two people with the same name are the same person.
- get_openprofileSays read-only
- The person as a portable profile file (logicsrc.com/openprofile): identity block, Accounts, Topics, a Broadcast section (logicsrc.com/openbroadcast) for every show they publish, corrected by the person once they have claimed it. Returns the Markdown and the parsed sections. Pass either the author's slug or a feed URL; with a feed URL you get the profile of the feed's owner.
- update_openprofileSays it can change data
- Edit a profile you have claimed. Send the whole file as `markdown` (everything in it becomes your word; a section you leave out is dropped) or a patch: `headline`, `identity` {Key: value, or null to remove}, `sections` {name: Markdown body, or null to drop}, `public`. Sections you do not mention stay as generated. Needs a credential in the Authorization header: one of your rssamplifier API keys, o
- claim_openprofileSays it can change data
- Say that an author in this directory is you, so you can correct the profile. Verified on the spot, no reviewer: the email behind your credential matches the address the author published about themselves, or the author's own site links back at the profile with rel="openprofile" or rel="me". Needs a credential in the Authorization header: an rssamplifier API key, or an OpenAccess bearer for `openpro
- directory_statsSays read-only
- How big the directory is, what it is made of, and whether the crawler is keeping up. `stale` is active feeds not read successfully in a day; `due` is a backlog that should drain within a tick or two. Answer this before concluding a feed is missing — it may simply not have been crawled yet.
- trending_topicsSays read-only
- Subjects English blogs and news sites used in headlines more than the week before, ranked. `count` is feeds, not posts, in a one in four sample, so it measures movement rather than coverage, and `prior_count` is the same figure for the week before. Updated daily. An empty list means the rollup has not got two days to compare yet.
- list_ringsSays read-only
- The OpenWebring rings hosted here (logicsrc.com/openwebring): one per well-covered topic, each an ordered circular list of member sites with next, previous and random hops. Every entry carries the ring page, the ring file, an OPML of the members' feeds, and how many members are listed and active. A member site may declare who makes it (human, ai or both); absent means it has not said.
- get_ringSays read-only
- A ring's members in ring order, each with its site, feed, status (active, pending or inactive) and, where the site declared them, made_by and disclosure. The same document as /ring/<slug>/openwebring.json. Use ring_next to follow a hop rather than computing one from this list.
- ring_nextSays read-only
- Which member a hop lands on, without following a redirect: the site after or before `from` in ring order, or a random one. `from` is a member site URL or its slug; omit it for a random active member. Pending and inactive members are listed by get_ring but skipped here, and the ring wraps around. Nothing is recorded about who asked.
- ring_embedSays read-only
- The copy-paste HTML a site puts in its footer to show it belongs to one or more webrings here: `<< Ring >>` per ring, previous / ring page / next, each hop measured from the member site given as `site` (its homepage). Returns a plain variant (bare links, the page styles them) and a styled one (inline styles), plus the raw links. No script, no images. Rings are slugs from list_rings.
- get_newsletterSays read-only
- RSSAmp's weekly email: when it goes (day and hour, UTC), the next send, how many accounts are on it, and the latest issue as sent (subject and text). Every account is on it unless it opted out.
- newsletter_previewSays read-only
- This week's digest as it would be built right now from the directory: new feeds, posts from the most-followed blogs, liked posts, webring activity. Read-only: nothing is stored or sent. `issue` is null when there is nothing to say yet.
- submit_feedSays it can change data
- Submit one URL or a list of them to RSSAmp. A site URL works as well as a feed URL: the feed is discovered from the page. Anyone may submit; there is no account and no review queue. One URL resolves in the call and the answer carries its page; a list may be queued, and the answer says which. Rate limited per caller.
- list_webhooksSays read-only
- Your webhook endpoints (url, event filters, on/off, failures) and the event types this site emits. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
- create_webhookSays it can change data
- Register an https URL to receive your alerts as signed POSTs (CloudEvents body, Standard Webhooks signature headers, plus x-rssamplifier-signature: sha256=<hex HMAC of the body>). Returns the endpoint and its signing secret (whsec_...), shown here once. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
- update_webhookSays it can change data
- Change an endpoint's url, events, description, or switch it on/off (turning it back on clears its failure count). Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
- delete_webhookSays it can change data
- Delete an endpoint and its delivery log. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
- test_webhookSays it can change data
- Send a signed webhook.test event to the endpoint now and report the HTTP status. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
- rotate_webhook_secretSays it can change data
- Mint a new signing secret for the endpoint and return it; the old one stops working at once. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
- webhook_deliveriesSays read-only
- Recent deliveries (status, attempts, last HTTP status or error, payload), for one endpoint or all of yours. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).
What it does
- Remote MCP endpoint
- Connects to AI clients over streamable HTTP at the site's /api/mcp address.
- Feed discovery from URLs
- Accepts a single URL, a list of URLs, or an OPML file and locates the feed for each blog.
- Per-blog pages
- Each blog gets a permanent page showing its latest summaries.
- Machine-readable exports
- The directory is available as JSON, OPML and plain text.
- Command-line access
- An install script provides terminal search by subject, post search and OPML export.
Good for
- Letting an AI agent find blogs on a topic and read their latest posts
- Exporting a list of feeds as OPML to move between feed readers
- Searching across many small blogs from a shell script
- Building a reading list of independent sites for research
rssamplifier FAQ
How do I connect to the MCP server?
The MCP registry entry lists a streamable HTTP remote at https://rssamp.com/api/mcp.
How are blogs added to the directory?
By submitting a URL, a list of URLs, or an OPML file on the site.
What formats is the directory available in?
The site says it is available as JSON, OPML and plain text.
How do I add rssamplifier to Claude Code?
Run this command in your terminal: claude mcp add --transport http rssamplifier https://rssamp.com/api/mcp
What are the best alternatives to rssamplifier?
The closest alternatives to rssamplifier are Parallel Search MCP, RSS Keyword Monitor, AgentFeed, Reddit MCP Server and Reddit Insights MCP.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Status and tools: checked automatically by AIPoweredBot on 19 November 2026.
- Install steps: from the official MCP Registry entry.
