@takara-ai/miru-code

MCPattested
v1.10.1TakaraMITUpdated 1d agonpmGitHub

Miru (見る) — hybrid code search for agents. Bun, TypeScript, Takara embeddings.

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
810Downloads/wk
11GitHub stars
2Forks
1d agoLast update
Reads these credentials
  • TAKARA_API_KEYAPI keyoptional

    Takara API key. Optional: without it, the MCP auth tool signs in with a device code.

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
AuthorTakara
LicenseMIT
Version1.10.1
Sourcenpm+mcp-registry
npm@takara-ai/miru-code
GitHubtakara-ai/miru-code
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 3625c24
Dependencies✓ 27 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv1.10.1 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 6, 2026

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

Tools

6 tools · none privileged
Statically extracted from the published packagev1.10.1 · 1d 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.

authNo description published

This tool published no description. Forge does not invent one.

searchNo description published

This tool published no description. Forge does not invent one.

locateNo description published

This tool published no description. Forge does not invent one.

expandNo description published

This tool published no description. Forge does not invent one.

find_relatedNo description published

This tool published no description. Forge does not invent one.

read_benchmarkNo description published

This tool published no description. Forge does not invent one.

0 of 6 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

Miru (見る) — hybrid code search for agents. Bun, TypeScript, Takara embeddings.

Keywords
code-searchsemantic-searchhybrid-searchmcpembeddingsbm25bunagentscursortakara
Alternatives
Comparing tool surfaces…

Tools exposed

6 tools · none 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.

Dependency tree

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

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

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

3 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

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

Topics

Related in search & retrieval