MCP server for wallabag read-it-later entries, tags, and annotations.
A Model Context Protocol (MCP) server for wallabag, the open-source read-it-later service. This server gives AI assistants a structured interface for common wallabag workflows: Verify connectivity and authentication with a tiny read-only health check List, filter, and page through saved articles Fetch entry metadata or full extracted content Archive/unarchive and star/unstar entries…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A Model Context Protocol (MCP) server for wallabag, the open-source read-it-later service. This server gives AI assistants a structured interface for common wallabag workflows: Verify connectivity and authentication with a tiny read-only health check List, filter, and page through saved articles Fetch entry metadata or full extracted content Archive/unarchive and star/unstar entries Reload/refetch article extraction List, create, and delete annotations wallabag is widely used in self-hosted…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.