llm-wiki-memory / security
Security review

Is llm-wiki-memory MCP safe to give an agent?

unknownunknownunknownhealthy

A factual risk summary built from llm-wiki-memory’s real tool surface, execution model, and verification history — not a vibe. Trust score 58/100.


01What it can do

No tool handshake yet — capability surface unverified.

0 tools observed

02Execution model

Transport not yet confirmed, so the execution model is unknown. Treat as untrusted until verified.

No runnable install method captured.


03Permissions & auth

No auth scopes captured yet (scope extraction runs during the sandboxed handshake, gated until configured). Treat unconfirmed scopes as unknown, not as “none.”


04Verification
handshakenot confirmed
runsmetadata:passed · metadata:passed
last_checked2026-06-29 07:32Z
sourcesGitHub repo search [p4]

Reduce the risk

Wrap llm-wiki-memory in a governed Loadout — scoped permissions, approval rules on write/destructive tools, and audit logging — instead of handing your agent raw access.

Build a governed Loadout

See also: full server page · setup · alternatives

Is llm-wiki-memory MCP safe? — risk & permissions — MCPExplorer