rss-publisher-mcp
Related Servers
Alternatives to rss-publisher-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables users to maintain append-only content history with verified publication and social follow-through outcomes, search for overlaps, and run read-only integrity verification of stored snapshots.16MIT
- AlicenseNot gradedqualityDmaintenanceEnables intelligent RSS feed management with AI-powered semantic search, advanced filtering, and a comprehensive reading workflow. Supports OPML parsing, article organization with status tracking, and token-efficient browsing of large feed collections.7 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to search a curated RSS/Atom catalog, subscribe to and collect feeds, and query collected articles through natural-language tools.2MIT
- AlicenseNot gradedqualityCmaintenanceProfessional RSS/Atom feed management system with AI-powered analytics including sentiment analysis, trend detection, auto-categorization, cross-source verification, automated scheduling, and content export capabilities.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables secure acquisition of itch.io game assets via official RSS feeds and authenticated Butler daemon downloads, and preview-gated publishing of game builds with hash-bound receipts and license verification.MIT
- AlicenseAqualityCmaintenanceEnables append-only revision projects with SHA-256-fingerprinted changes, style heuristics, human approval checkpoints, and draft-only WordPress export handoffs.9MIT
TDQS
Scored across 16 tools
Most tools map cleanly to distinct lifecycle actions: create, update, correct, retract, unpublish, republish, and feed/validation operations are well separated. The main ambiguity is between correct_entry and update_entry, since both modify an entry while preserving its identity; the correction framing helps but could overlap for simple edits.
All tools follow a consistent snake_case verb_noun pattern with clear verbs such as get, list, create, update, validate, audit, and rebuild. Even specialized actions like correct_entry, retract_entry, unpublish_entry, and republish_entry use the same convention, making the set predictable.
Sixteen tools is slightly above the usual sweet spot, but each covers a distinct facet of running an RSS publisher: configuration, entry lifecycle, corrections/retractions, validation/audit, rebuild, batching, and assets. It is not bloated, though a few tools like find_similar_active_entries add extra surface beyond a minimal CRUD set.
The entry lifecycle is well covered with create, read, update, unpublish, republish, correct, retract, and batch publish, plus feed configuration, validation/audit, and rebuild. Minor gaps exist around asset management since only get_asset is exposed and binary upload is handled outside the MCP server; there is also no explicit physical delete, though retract/unpublish appear to be intentional immutable alternatives.