ToolTrust
A2/100
Smithery

mi4uu-brain-md

mcpsmithery

@Smithery

A local-first second brain for you — and for your AI agents.

By Smithery | 28 findings | Scanned 7/3/2026 | tooltrust-scanner/v0.3.19

2 Low26 Info

Risk Summary

Safe With Normal Controls

Dep Visibility is the main signal, but overall risk remains within an acceptable range.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (28)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×2

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    search_notescontext_for_query

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-002

    ⚠️Excessive Permissions ×9

    declared capabilities: network access

    search_notescontext_for_query

    declared capabilities: filesystem access

    read_notelist_notesget_backlinkswrite_noteappend_notefind_relatedsemantic_outline

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×16

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    search_notessimilar_notesread_notelist_notesget_backlinkslist_tagsget_taskswrite_noteappend_notefind_similar_tasksfind_relatedsemantic_outlinecontext_for_queryfind_orphansweekly_digestcompare_notes

    Fix: Review and remediate the identified issue.

  • InfoAS-010

    🔑Insecure Secret Handling

    context_for_query:input parameter "budget_tokens" accepts a credential (informational; not evidence of insecure handling)

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y mi4uu-brain-md"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)