Documentation Search Enhanced MCP Server
documentation-search-enhanced
PyPI
v1.9.0
Published by anton-prosterity — 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.
Enhanced MCP server for searching documentation with OSINT vulnerability scanning, security analysis, and AWS-style deployment
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 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Unsafe deserialization MTC-SRC-007 | permissions |
2. Client adoption risk — 94 − 4 = 90. 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
medium Unsafe deserialization (src/documentation_search_enhanced/vector_search.py)MTC-SRC-007
In the server's implementation (`src/documentation_search_enhanced/vector_search.py:276`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: s f: data = pickle.load(f) self.doc_store = data["doc_store"] self.next_id = data["n
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 src/documentation_search_enhanced/vector_search.py
Tools 23
Each tool and what it can reach — statically extracted from the published source.
get_environment_configreads sensitive dataclear_cacheno sensitive capabilitycompare_library_securityno sensitive capabilityfiltered_searchno sensitive capabilitygenerate_project_starterno sensitive capabilityget_cache_statsno sensitive capabilityget_code_examplesno sensitive capabilityget_current_configno sensitive capabilityget_docsno sensitive capabilityget_learning_pathno sensitive capability
Show 13 more tools ↓
get_security_summaryno sensitive capabilityhealth_checkno sensitive capabilitymanage_dev_environmentno sensitive capabilitypreindex_docsno sensitive capabilityscan_library_vulnerabilitiesno sensitive capabilityscan_project_dependenciesno sensitive capabilitysemantic_searchno sensitive capabilitysnyk_license_checkno sensitive capabilitysnyk_monitor_projectno sensitive capabilitysnyk_scan_libraryno sensitive capabilitysnyk_scan_projectno sensitive capabilitysuggest_librariesno sensitive capabilitysuggest_secure_librariesno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (23 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 1
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 |
|---|---|---|---|---|
v1.9.0 latest |
A 90/100 | 1 | 1.13.0 | 2026-08-25 |
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 documentation-search-enhanced --online --registry pypiMore in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).