Linkwarden MCP Server
linkwarden-mcp
PyPI
v0.1.6
Published by flumpiey — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Linkwarden bookmarks: read-first search and preserved content, with opt-in write, delete, and collection-delete tools.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (tests/test_sdist_contents.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_sdist_contents.py:35`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: if MCP holds them. subprocess.run( [sys.executable, "-m", "hatch", "build", f"--target={target}"],
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_sdist_contents.py
Tools 17
Each tool and what it can reach — statically extracted from the published source.
read_link_contentingests untrusted inputalign_tags_with_similar_linksno sensitive capabilityanalyze_collection_overlapno sensitive capabilityfind_duplicate_linksno sensitive capabilityfind_unsorted_linksno sensitive capabilityget_library_overviewno sensitive capabilityget_linkno sensitive capabilityget_sorting_dashboardno sensitive capabilitylist_collectionsno sensitive capabilitylist_tagsno sensitive capability
Show 7 more tools ↓
recommend_collection_for_linksno sensitive capabilitysearch_linksno sensitive capabilitysuggest_collection_for_urlno sensitive capabilitysuggest_collection_structureno sensitive capabilitysuggest_links_for_collectionno sensitive capabilitysuggest_tags_for_linkno sensitive capabilitytriage_linksno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 3
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.6 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-28 |
v0.1.5 |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
v0.1.4 |
A 96/100 | 1 | 1.12.1 | 2026-08-04 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan linkwarden-mcp --online --registry pypiMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.