in-memoria

MCPcommunity
v0.6.0Piyush AiraniMITUpdated 9mo agonpm

Persistent intelligence infrastructure for agentic development

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 →
160Downloads/wk
9mo agoLast update
Reads these credentials
  • OPENAI_API_KEYAPI keyoptional

    Optional OpenAI API key for embeddings (falls back to local transformers.js)

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
AuthorPiyush Airani
LicenseMIT
Version0.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
Dependencies60 resolved · 1 with advisories
Tool surface14 tools · none privileged
Security scan⚠ Warnings (1)v0.6.0 · 1d agoHow well does this scan work?
EvalsNone
IndexedAug 28, 2026

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

Tools

14 tools · none privileged
Statically extracted from the published packagev0.6.0 · 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.

auto_learn_if_neededAutomatically learn from codebase if intelligence data is missing or stale. Call this first before using other In-Memoria tools - it's a no-op if data already exists. Includes project setup and verification. Perfect for seamless agent integration.

Automatically learn from codebase if intelligence data is missing or stale. Call this first before using other In-Memoria tools - it's a no-op if data already exists. Includes project setup and verification. Perfect for seamless agent integration.

No input schema was published for this tool.

analyze_codebaseOne-time analysis of a specific file or directory. Returns AST structure, complexity metrics, and detected patterns for that path only. For project-wide understanding, use get_project_blueprint instead (faster, uses learned intelligence). Use this for deep-dive analysis of a specific file you're cu…

One-time analysis of a specific file or directory. Returns AST structure, complexity metrics, and detected patterns for that path only. For project-wide understanding, use get_project_blueprint instead (faster, uses learned intelligence). Use this for deep-dive analysis of a specific file you're cu…

No input schema was published for this tool.

search_codebaseSearch for code by text matching or patterns. Use "text" type for finding specific strings/keywords in code. Use "pattern" type for regex/AST patterns. Note: For "where should I work?" or "what files to modify?" questions, use predict_coding_approach instead - it provides intelligent file routing w…

Search for code by text matching or patterns. Use "text" type for finding specific strings/keywords in code. Use "pattern" type for regex/AST patterns. Note: For "where should I work?" or "what files to modify?" questions, use predict_coding_approach instead - it provides intelligent file routing w…

No input schema was published for this tool.

learn_codebase_intelligenceBuild intelligence database from codebase (one-time setup, ~30-60s). Required before using predict_coding_approach, get_project_blueprint, or get_pattern_recommendations. Re-run with force=true if codebase has significant changes. Most users should use auto_learn_if_needed instead - it runs this au…

Build intelligence database from codebase (one-time setup, ~30-60s). Required before using predict_coding_approach, get_project_blueprint, or get_pattern_recommendations. Re-run with force=true if codebase has significant changes. Most users should use auto_learn_if_needed instead - it runs this au…

No input schema was published for this tool.

get_semantic_insightsSearch for code-level symbols (variables, functions, classes) by name and see their relationships, usage patterns, and evolution. Use this to find where a specific function/class is defined, how it's used, or what it depends on. Searches actual code identifiers (e.g., "DatabaseConnection", "process…

Search for code-level symbols (variables, functions, classes) by name and see their relationships, usage patterns, and evolution. Use this to find where a specific function/class is defined, how it's used, or what it depends on. Searches actual code identifiers (e.g., "DatabaseConnection", "process…

No input schema was published for this tool.

get_pattern_recommendationsGet coding pattern recommendations learned from this codebase. Use this when implementing new features to follow existing patterns (e.g., "create a new service class", "add API endpoint"). Returns patterns like Factory, Singleton, DependencyInjection with confidence scores and actual examples from…

Get coding pattern recommendations learned from this codebase. Use this when implementing new features to follow existing patterns (e.g., "create a new service class", "add API endpoint"). Returns patterns like Factory, Singleton, DependencyInjection with confidence scores and actual examples from…

No input schema was published for this tool.

predict_coding_approachFind which files to modify for a task using intelligent file routing. Use this when the user asks "where should I...", "what files...", or "how do I add/implement..." to route them directly to the relevant files without exploration. Returns target files, suggested starting point, and reasoning base…

Find which files to modify for a task using intelligent file routing. Use this when the user asks "where should I...", "what files...", or "how do I add/implement..." to route them directly to the relevant files without exploration. Returns target files, suggested starting point, and reasoning base…

No input schema was published for this tool.

get_developer_profileGet patterns and conventions learned from this codebase's code style. Shows frequently-used patterns (DI, Factory, etc.), naming conventions, and architectural preferences. Use this to understand "how we do things here" before writing new code. Note: This is about the codebase's style, not individu…

Get patterns and conventions learned from this codebase's code style. Shows frequently-used patterns (DI, Factory, etc.), naming conventions, and architectural preferences. Use this to understand "how we do things here" before writing new code. Note: This is about the codebase's style, not individu…

No input schema was published for this tool.

contribute_insightsLet AI agents save discovered insights (bug patterns, optimizations, best practices) back to In-Memoria for future reference. Use this when you discover a recurring pattern, potential bug, or refactoring opportunity that other agents/sessions should know about. Creates organizational memory across…

Let AI agents save discovered insights (bug patterns, optimizations, best practices) back to In-Memoria for future reference. Use this when you discover a recurring pattern, potential bug, or refactoring opportunity that other agents/sessions should know about. Creates organizational memory across…

No input schema was published for this tool.

get_project_blueprintGet instant project blueprint - eliminates cold start exploration by providing tech stack, entry points, key directories, and architecture overview

Get instant project blueprint - eliminates cold start exploration by providing tech stack, entry points, key directories, and architecture overview

No input schema was published for this tool.

get_system_statusGet comprehensive system status including intelligence data, performance metrics, and health indicators

Get comprehensive system status including intelligence data, performance metrics, and health indicators

No input schema was published for this tool.

get_intelligence_metricsGet detailed metrics about the intelligence database and learning state

Get detailed metrics about the intelligence database and learning state

No input schema was published for this tool.

get_performance_statusGet performance metrics including database size, query times, and resource usage

Get performance metrics including database size, query times, and resource usage

No input schema was published for this tool.

health_checkVerify In-Memoria setup and configuration for a project. Checks database accessibility, project structure, and API keys.

Verify In-Memoria setup and configuration for a project. Checks database accessibility, project structure, and API keys.

No input schema was published for this tool.

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

Persistent intelligence infrastructure for agentic development

Keywords
mcpmcp-servermodel-context-protocolaiai-assistantcodebase-intelligencecode-analysissemantic-searchpattern-learningdeveloper-toolsclaudecopilot
Alternatives
Comparing tool surfaces…

Dependency tree

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

60 packages resolved · 10 direct · 1 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

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

+61 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