locus-mcp

MCPcommunity
v0.9.0io.github.Nano-NimbusUnknownUpdated 7mo agoGitHub

Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7mo agoLast update
Package
Authorio.github.Nano-Nimbus
LicenseUnknown
Version0.9.0
Sourcemcp-registry
GitHubNano-Nimbus/locus
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · 1 privileged
Security scan✓ Cleanv0.2.0 · 20d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · 1 privileged
Statically extracted from the published packagev0.2.0 · 20d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

restricted_execprivilegedExecute restricted commands (rg, readfile, tree, ls, glob) in parallel.

Execute restricted commands (rg, readfile, tree, ls, glob) in parallel.

No input schema was published for this tool.

answerFinal answer with relevant files and line ranges.

Final answer with relevant files and line ranges.

No input schema was published for this tool.

locus_mcp_searchAI-driven semantic code search (Devstral multi-turn + Locus native Graph/Hybrid retrieval).

AI-driven semantic code search (Devstral multi-turn + Locus native Graph/Hybrid retrieval).

No input schema was published for this tool.

locus_index_statusInspect Locus native Graph/Hybrid index freshness, ignore rules, file watching, and incremental sync state.

Inspect Locus native Graph/Hybrid index freshness, ignore rules, file watching, and incremental sync state.

No input schema was published for this tool.

extract_windsurf_keyExtract Windsurf API Key from local installation.

Extract Windsurf API Key from local installation.

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.