Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

rssamplifier

REMOTE · RSSAMP.COM

Small-web feed directory (rssamp.com)

Available components

+4 this week 72 Trust /100

Last scanned (21 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Recent critical change

Authorization (19 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3611 tokens (~120/item across 30 items; 29 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +16
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 18 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 +63
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 83 functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 100 functional
    • First check of Schema quality: good functional
  • 11 Nov 26 4

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://rssamp.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rssamp.com CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 6319a3baed57d393a7819faa56b797fbdad
SANs: rssamp.com, www.rssamp.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rssamp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
rssamp.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rssamp.com/api/mcp Verified 200
http (plaintext) http://rssamp.com/api/mcp HTTPS enforced 301 https://rssamp.com/api/mcp
MCP tools · 29 exposed · ~3,244 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
claim_openprofile ~107

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 `openprofile:edit`.

NameTypeReqDescription
slugstringyesThe author's slug.

No output schema declared.

No examples provided.

create_webhook ~142

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

NameTypeReqDescription
descriptionstring–What it is, for your own list.
eventsarray–Event patterns; default ["*"]. The one event is posts.published.
urlstringyeshttps URL that resolves to a public address.

No output schema declared.

No examples provided.

delete_webhook ~59

Delete an endpoint and its delivery log. Needs one of your rssamplifier API keys in the Authorization header (Bearer rsa_..., from /account).

NameTypeReqDescription
idstringyesThe webhook endpoint id (wh_...), from list_webhooks.

No output schema declared.

No examples provided.

directory_stats ~76

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_author ~55

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.

NameTypeReqDescription
slugstringyesThe author's slug in this directory.

No output schema declared.

No examples provided.

get_feed ~127

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

NameTypeReqDescription
limitinteger–Posts. Default 50.
slugstringyesThe feed's slug in this directory.

No output schema declared.

No examples provided.

get_newsletter ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_openprofile ~122

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.

NameTypeReqDescription
feedstring–A feed URL; the owner of that feed is looked up.
slugstring–The author's slug in this directory.

No output schema declared.

No examples provided.

get_ring ~88

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.

NameTypeReqDescription
slugstringyesThe ring slug, from list_rings.

No output schema declared.

No examples provided.

get_topic ~160

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, each once, with `topics` naming the known ones and `unknown` the rest.

NameTypeReqDescription
keywordstringyesThe topic, in any spelling — or several, separated by commas.
limitinteger–Default 100.
offsetinteger–Default 0.

No output schema declared.

No examples provided.

list_authors ~235

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 search names. Role mailboxes like info@ are never returned: they are dropped at extraction, so an address here belongs to a person.

NameTypeReqDescription
limitinteger–Default 50.
minConfidencenumber–How sure the attribution must be, 0 to 1. Default 0.6, which is what the site itself publishes. Lower it for the long tail, and expect some of it to be wrong.
networkstring–Only people with a link on this network, e.g. "email" or "fediverse".
offsetinteger–Default 0.
querystring–Search names.

No output schema declared.

No examples provided.

list_feeds ~100

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.

NameTypeReqDescription
kindstring–Only feeds of this category. Omit for all of them.
limitinteger–Default 50.
offsetinteger–Default 0.

No output schema declared.

No examples provided.

list_rings ~98

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_topics ~165

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.

NameTypeReqDescription
limitinteger–Default 100.
mininteger–Only topics at least this many feeds cover. Default 2.
offsetinteger–Default 0.
querystring–Search the topic index. A phrase works as well as a slug — "quantum physics" and "quantum-physics" are the same search. Matches are ranked: the exact topic, then topics starting with the term, then t…

No output schema declared.

No examples provided.

list_webhooks ~54

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

newsletter_preview ~62

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

random_feed ~39

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_post ~149

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 to be redistributed (reason publisher-opt-out) comes back with the feed's summary and a reason instead — never an error.

NameTypeReqDescription
feedstringyesThe feed's slug.
guidstringyesThe post's guid, as returned by the other tools.

No output schema declared.

No examples provided.

ring_embed ~162

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.

NameTypeReqDescription
randomboolean–Add the random-site link. Default false.
ringsarrayyesRing slugs, in the order the rows should appear.
sitestring–The member site's homepage, e.g. https://example.com/. Omit for a placeholder.

No output schema declared.

No examples provided.

ring_next ~127

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.

NameTypeReqDescription
directionstring–Default next.
fromstring–The member site the reader is on: its URL or its slug.
slugstringyesThe ring slug, from list_rings.

No output schema declared.

No examples provided.

rotate_webhook_secret ~72

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

NameTypeReqDescription
idstringyesThe webhook endpoint id (wh_...), from list_webhooks.

No output schema declared.

No examples provided.

search ~195

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 match set by category under `categories`, and `kind` asks for one of them — the podcast episodes on a subject rather than the writing.

NameTypeReqDescription
kindstring–Only results from feeds of this category. Omit for all of them, and read `categories` in the reply to see what the other kinds hold.
limitinteger–Results of each kind. Default 30.
modestring–Require every term (default) or any one of them.
querystringyesWhat to search for.

No output schema declared.

No examples provided.

submit_feed ~97

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.

NameTypeReqDescription
urlsarrayyesFeed or site URLs. One is fine.

No output schema declared.

No examples provided.

test_webhook ~67

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

NameTypeReqDescription
idstringyesThe webhook endpoint id (wh_...), from list_webhooks.

No output schema declared.

No examples provided.

topic_posts ~129

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 river across all of them.

NameTypeReqDescription
keywordstringyesThe topic, in any spelling — or several, separated by commas.
limitinteger–Default 50.

No output schema declared.

No examples provided.

trending_topics ~109

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.

NameTypeReqDescription
limitinteger–Default 50.
windowinteger–Days per side of the comparison. Default 7.

No output schema declared.

No examples provided.

update_openprofile ~208

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, or an OpenAccess bearer for `openprofile:edit` (openaccess.logicsrc.com). Claim first with claim_openprofile.

NameTypeReqDescription
headlinestring––
identityobject––
markdownstring–The whole OpenProfile.md, replacing every section.
namestring––
prosestring––
publicboolean–false hides the file; the author page stays.
sectionsobject––
slugstringyesThe author's slug.

No output schema declared.

No examples provided.

update_webhook ~105

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

NameTypeReqDescription
descriptionstring––
enabledboolean––
eventsarray––
idstringyesThe webhook endpoint id (wh_...), from list_webhooks.
urlstring––

No output schema declared.

No examples provided.

webhook_deliveries ~78

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

NameTypeReqDescription
idstring–Only this endpoint; omit for every endpoint.
limitinteger––

No output schema declared.

No examples provided.

Install

How do I install the rssamplifier MCP server?

rssamplifier is a hosted endpoint at https://rssamp.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · rssamp.com

# add to Claude Code
claude mcp add --transport http com-profullstack-rssamplifier 'https://rssamp.com/api/mcp'
Common questions

What is the rssamplifier MCP server?

rssamplifier is an MCP server listed in the public MCP registry as com.profullstack/rssamplifier. Small-web feed directory (rssamp.com). This page covers its hosted endpoint (https://rssamp.com/api/mcp).

Is the rssamplifier MCP server safe to use?

rssamplifier scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the rssamplifier MCP server expose?

rssamplifier exposes 29 tools: search, list_feeds, get_feed, list_topics, get_topic, and 24 more. Their descriptions and schemas cost roughly 3,244 tokens of context every time the server is loaded.

Does the rssamplifier MCP server require authentication?

No. We connected to rssamplifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the rssamplifier MCP server still maintained?

rssamplifier is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the rssamplifier MCP server?

VerifyMCP ran 13 checks on rssamplifier, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.