dsh-codebase-chat-mcp

MCPcommunity

v0.10.0io.github.shinzarou-engMITUpdated 18d agonpm GitHub

Local-first codebase intelligence: cited answers, audits, reports. EN/FR.

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 →

348Downloads/wk

2GitHub stars

1Forks

18d agoLast update

Package

Authorio.github.shinzarou-eng

LicenseMIT

Version0.10.0

Sourcenpm+mcp-registry

npmdsh-codebase-chat-mcp

GitHubshinzarou-eng/dsh-codebase-chat

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—

Dependencies60 resolved · 1 with advisories

Tool surface13 tools · none privileged

Security scan⚠ Warnings (2)v0.8.7 · 19d agoHow well does this scan work?

HIGHsharp@0.32.6sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591 · transitive HIGHsharp@0.32.6sharp: Vulnerabilities in libheif: GHSA-g89c-p67h-r497 and GHSA-2jg2-4ch7-h545 · transitive

EvalsNone

IndexedSep 12, 2026

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

Tools

13 tools · none privileged

Statically extracted from the published packagev0.8.7 · 19d 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.

Filter toolsPrivileged only

codebase_intelligencePro technical audit: architecture, tech debt, opportunities and creative ideas.

Pro technical audit: architecture, tech debt, opportunities and creative ideas.

No input schema was published for this tool.

codebase_reportStrategic board report with SWOT, scorecards and 90-day roadmap.

Strategic board report with SWOT, scorecards and 90-day roadmap.

No input schema was published for this tool.

codebase_auditNon-conformities and technical-debt audit with concrete fixes.

Non-conformities and technical-debt audit with concrete fixes.

No input schema was published for this tool.

codebase_tasksGenerate a prioritized TASKS.md with sprints and Before/After.

Generate a prioritized TASKS.md with sprints and Before/After.

No input schema was published for this tool.

codebase_ceoOne-page executive brief with metrics, risks and killer moves.

One-page executive brief with metrics, risks and killer moves.

No input schema was published for this tool.

codebase_playerUser journey and playthrough UX analysis.

User journey and playthrough UX analysis.

No input schema was published for this tool.

codebase_searchSearch files and symbols by term or pattern.

Search files and symbols by term or pattern.

No input schema was published for this tool.

codebase_explainExplain how a file or symbol works.

Explain how a file or symbol works.

No input schema was published for this tool.

codebase_refactorPropose a refactor for a file or function.

Propose a refactor for a file or function.

No input schema was published for this tool.

codebase_chatOpen Q/A on the codebase.

Open Q/A on the codebase.

No input schema was published for this tool.

codebase_creaGenerate creative ideas, slogans or marketing concepts from the code.

Generate creative ideas, slogans or marketing concepts from the code.

No input schema was published for this tool.

codebase_healthDeterministic static analysis: circular deps, dead code, duplication, complexity hotspots, health score. Returns findings directly — no LLM call.

Deterministic static analysis: circular deps, dead code, duplication, complexity hotspots, health score. Returns findings directly — no LLM call.

No input schema was published for this tool.

codebase_impactBlast-radius analysis: which files transitively depend on a target file — what breaks if it changes. Deterministic, no LLM call.

Blast-radius analysis: which files transitively depend on a target file — what breaks if it changes. Deterministic, no LLM call.

No input schema was published for this tool.

13 of 13 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

Local-first codebase intelligence: cited answers, audits, reports. EN/FR.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

13 tools · none privileged · observed 2026-09-13 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

codebase_intelligence
codebase_report
codebase_audit
codebase_tasks
codebase_ceo
codebase_player
codebase_search
codebase_explain
codebase_refactor
codebase_chat
codebase_crea
codebase_health
codebase_impact

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

Dependency tree

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

60 packages resolved · 2 direct · 1 carrying advisories Resolution stops at depth 4 and 60 packages.

dsh-codebase-chat0.25.68 dependencies
- figlet1.11.4+1 not drawn
- @babel/types8.0.5+2 not drawn
- @babel/parser8.0.51 dependency
  - @babel/types8.0.5shown above+2 not drawn
- gpt-tokenizer4.0.0
- @babel/traverse8.0.5+5 not drawn2 dependencies
  - @babel/types8.0.5shown above+2 not drawn
  - @babel/parser8.0.5shown above
- web-tree-sitter0.22.6
- tree-sitter-wasms0.1.131 dependency
  - tree-sitter-wasms0.1.13shown above
- @xenova/transformers2.17.2+2 not drawn1 dependency
  - sharp0.32.6incompleteHIGH GHSA-f88m-g3jw-g9cj HIGH GHSA-rgj7-g3m4-5g8c
@modelcontextprotocol/sdk1.30.0+4 not drawn13 dependencies
- ajv8.20.0+4 not drawn
- zod4.6.3
- cors2.8.6+2 not drawn
- hono4.13.7
- jose6.2.12
- express5.2.1incomplete+19 not drawn
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete
- eventsource3.0.7incomplete
- content-type1.0.5
- pkce-challenge5.0.1
- @hono/node-server2.1.1

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

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

package cap reached: 75

body-parser ^2.2.1 — required by express@5.2.1package cap reached
escape-html ^1.0.3 — required by express@5.2.1package cap reached
http-errors ^2.0.0 — required by express@5.2.1package cap reached
on-finished ^2.4.1 — required by express@5.2.1package cap reached
content-type ^1.0.5 — required by express@5.2.1package cap reached
finalhandler ^2.1.0 — required by express@5.2.1package cap reached
range-parser ^1.2.1 — required by express@5.2.1package cap reached
serve-static ^2.2.0 — required by express@5.2.1package cap reached
cookie-signature ^1.2.1 — required by express@5.2.1package cap reached
merge-descriptors ^2.0.0 — required by express@5.2.1package cap reached
content-disposition ^1.0.0 — required by express@5.2.1package cap reached
bytes ~3.1.2 — required by raw-body@3.0.2package cap reached

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

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