wallabag-mcp@0.1.0
VERIFIED· install onlyPublisher claims: "Model Context Protocol server for wallabag read-it-later instances" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 4 of 4 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
DEEPSEEK_API_KEYWALLABAG_ACCESS_TOKENWALLABAG_CLIENT_SECRETWALLABAG_PASSWORDWALLABAG_REFRESH_TOKENConfiguration, not credentials: WALLABAG_BASE_URL, WALLABAG_CLIENT_ID, WALLABAG_TIMEOUT, WALLABAG_USERNAME- Where it talks to
- wallabag.org, wallabag.it (its own)Also deepseek.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names deepseek.com as well as its own vendor. The guard injects DEEPSEEK_API_KEY, WALLABAG_ACCESS_TOKEN, WALLABAG_CLIENT_SECRET, WALLABAG_PASSWORD, WALLABAG_REFRESH_TOKEN only into requests to wallabag.org (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-21 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.load_env(Path.home() / ".hermes" / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.targets.append(("aeon_ultimate", "http://192.168.68.164:8000/v1", "aeon-ultimate", "default"))Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for wallabag-mcp@0.1.0 as of 22 min ago. This is the package itself, not its dependencies.