opengrok-mcp-server

MCPcommunity
v9.6.0Rudra RoyPolyForm-Noncommercial-1.0.0Updated 19d agonpmGitHub

MCP server bridging OpenGrok search engine with AI for instant context across massive codebases

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 →
96Downloads/wk
8GitHub stars
3Forks
19d agoLast update
Reads these credentials
  • OPENGROK_PASSWORDAPI keyoptional

    OpenGrok authentication password. Prefer storing via OS keychain using 'npx opengrok-mcp-server setup'.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorRudra Roy
LicensePolyForm-Noncommercial-1.0.0
Version9.6.0
Sourcenpm+mcp-registry
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 surface—
Security scan✓ Cleanv9.6.0 · 18d agoHow well does this scan work?
EvalsNone
IndexedSep 16, 2026

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

Tools

Source not readable18d ago

The published package tarball could not be read at scan time (Cannot create a Buffer larger than 62914560 bytes), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

MCP server bridging OpenGrok search engine with AI for instant context across massive codebases

Keywords
opengrokcode searchcopilotmcpmodel context protocolmodel-context-protocolaigithub-copilotcode-search
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-16 — observed resolution, not a publisher declaration.

60 packages resolved · 18 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

91 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+79 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in search & retrieval