Mentu Navigator — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Mentu read-only repository navigation with range provenance: Do secret-path exclusions and ranked line evidence remain intact as navigation and impact tools change?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Navigate a local source repository using BM25 ranking and evidence-linked file ranges.

What we know

Read-only repo navigation and progressive disclosure; BM25 locator with registered evidence. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

mentu-navigator 1.1.1 published 2026-08-22T19:44:24.824Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read-only repository navigation within configured local paths
No hosted credential indicated for local repository indexing
Sensitive access: Local source code, Repository path metadata

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do secret-path exclusions and ranked line evidence remain intact as navigation and impact tools change?

The bounded review of the publisher's documented Mentu read-only repository navigation with range provenance and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.
Read-only repository navigation within configured local paths
No hosted credential indicated for local repository indexing
Source repository remains local; telemetry is local JSONL and can be disabled.
Sensitive access: Local source code, Repository path metadata
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
cost: plans, pay-per-call charges, and payment authorization details
verified direct MCP executable invocation for npx -p
Does not edit repositories
Local telemetry records may be written independently of read-only repository access
CLI and MCP binaries differ; plain npx package resolution is not sufficient
Do not use npx mentu-navigator directly: the package and executable names differ. Verify MCP launch syntax for the chosen client.

Original activity observations

mentu-navigator 1.1.1 published 2026-08-22T19:44:24.824Z

Technical identity

npm/mentu-navigator

Exact implementation source: https://www.npmjs.com/package/mentu-navigator ↗
Reviewed resource type: MCP Server
Repository identity: mentu-ai/mentu-navigator
Package identity: npm:mentu-navigator

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
mentu-navigator
Recorded package identity, distribution or download evidence.
GitHub repository ↗
mentu-ai/mentu-navigator
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Local code/project navigation permissions apply; no remote credentials implied.
Install documentation is not a guarantee of current package/runtime compatibility.
Publisher provides explicit npm package to binary mapping and MCP client JSON. Requires Node.js 20+.
2026-10-13 targeted publisher npm README plus official repository/docs where specified; static research, not runtime test.
Normalized from the publisher-described client registration; not runtime tested and not a Codex TOML config.
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npm install -g mentu-navigator
Configure / authenticate
MCP100 setup guide
Use `mentu-nav setup --target all` or register installed binary `mentu-navigator-mcp` in MCP host; plain npx mentu-navigator does not run this CLI.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Set client stdio command `npx` and args ["-y", "-p", "mentu-navigator", "mentu-navigator-mcp"], or use installed binary `mentu-navigator-mcp`. `mentu-nav` is the CLI binary; bare `npx mentu-navigator` is not the MCP command.
Previously reviewed configuration / prerequisites: Requires Node.js 20+.
{ "mcpServers": { "mentu-navigator": { "args": [ "-y", "-p", "mentu-navigator", "mentu-navigator-mcp" ], "command": "npx" } } }
Check connection
Suggested check
mentu-nav doctor --human; confirm MCP tool discovery.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `mentu-navigator` in Claude Code, remove its exact client entry with `claude mcp remove mentu-navigator`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly. For an explicitly globally installed package (not npx-only), npm uninstall -g mentu-navigator.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove mentu-navigator

Official Documentation & Sources

What it does

Read-only repo navigation and progressive disclosure; BM25 locator with registered evidence. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Navigate a local source repository using BM25 ranking and evidence-linked file ranges.

Representative uses

Find relevant code locations
Retrieve ranked file/line evidence
Orient agents to unfamiliar codebases

Limitations

Does not edit repositories
Local telemetry records may be written independently of read-only repository access
CLI and MCP binaries differ; plain npx package resolution is not sufficient
Do not use npx mentu-navigator directly: the package and executable names differ. Verify MCP launch syntax for the chosen client.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: No hosted credential indicated for local repository indexing
Permissions: Read-only repository navigation within configured local paths
Data handling: Source repository remains local; telemetry is local JSONL and can be disabled.
Cost: Not documented in the reviewed sources
Risk and cautions: Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Local source code Repository path metadata
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Find relevant code locations; Retrieve ranked file/line evidence; Orient agents to unfamiliar codebases.

What authentication is documented?

No hosted credential indicated for local repository indexing

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only repository navigation within configured local paths

What data-handling boundary should I consider?

Source repository remains local; telemetry is local JSONL and can be disabled. Recorded sensitive-access context: Local source code; Repository path metadata.

What limitations and risks should I check before use?

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent. Does not edit repositories. Local telemetry records may be written independently of read-only repository access. CLI and MCP binaries differ; plain npx package resolution is not sufficient. Do not use npx mentu-navigator directly: the package and executable names differ. Verify MCP launch syntax for the chosen client. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.